for the availability of IPs sorting the matching IPAddressPools
                  by priority, starting from the highest to the lowest. If multiple
                  IPAddressPools have the same priority, choice will be random.
                properties:
                  namespaceSelectors:
                    description: NamespaceSelectors list of label selectors to select

						><a class="nav-link active" href="${installationLink}" target="_olh"><em
								class="fa fa-exclamation-triangle text-warning"
							></a></li>
					</c:if>
					<c:choose>
						<c:when test="${!empty username && username != 'guest'}">
							<li class="nav-item">
								<div class="dropdown">
									<a class="nav-link dropdown-toggle" data-toggle="dropdown"

						><a class="nav-link active" href="${installationLink}" target="_olh"><em
								class="fa fa-exclamation-triangle text-warning"
							></a></li>
					</c:if>
					<c:choose>
						<c:when test="${!empty username && username != 'guest'}">
							<li class="nav-item">
								<div class="dropdown">
									<a class="nav-link dropdown-toggle" data-toggle="dropdown"

								><a class="nav-link active" href="${installationLink}" target="_olh"><em
										class="fa fa-exclamation-triangle text-warning"
									></a></li>
							</c:if>
							<c:choose>
								<c:when test="${!empty username && username != 'guest'}">
									<li class="nav-item">
										<div class="dropdown">
											<a class="nav-link dropdown-toggle" data-toggle="dropdown"

				</div>
			</div>
		</c:forEach>
		<c:choose>
			<c:when test="${f:h(allRecordCount) != 0}">
				<jsp:include page="searchResults.jsp" />
				<div class="text-right">
					<a href="#"><la:message key="labels.footer_back_to_top" /></a>
				</div>
			</c:when>
			<c:otherwise>
				<jsp:include page="searchNoResult.jsp" />
			</c:otherwise>
		</c:choose>
	</main>
	<jsp:include page="footer.jsp" />

global.jwtPolicy=first-party-jwt ``` manifests/charts/UPDATING-CHARTS.md # Updating charts and values.yaml ## Acceptable Pull Requests Helm charts `values.yaml` represent a complex user facing API that tends to grow uncontrollably over time due to design choices in Helm. The underlying Kubernetes resources we configure have 1000s of fields; given enough users and bespoke use cases, eventually someone will want to customize every one of those fields. If all fields are exposed in `values.yaml`, we end up with...

        By asking questions in a structured way (following this) it will be much easier to help you.

        And there's a high chance that you will find the solution along the way and you won't even have to submit it and wait for an answer. 😎

                                        <tr>
                                            <th style="width: 25%">${f:h(info.key)}</th>
                                            <c:choose>
                                                <c:when test="${info.key == 'Query ID'}">
                                                    <td><la:link

    render: Text
    value: |
      counter: gopls/bug
      title: Gopls bug reports
      description: Stacks of bugs encountered on the gopls server.
      type: partition, histogram, stack # choose only one.
      program: golang.org/x/tools/gopls
      counter: gopls/bug
      depth: 16  # only if type is stack.
      version: v0.13.0  # the first binary version containing this counter.
  validations:

								><a class="nav-link active" href="${installationLink}" target="_olh"><em
										class="fa fa-exclamation-triangle text-warning"
									></a></li>
							</c:if>
							<c:choose>
								<c:when test="${!empty username && username != 'guest'}">
									<li class="nav-item">
										<div class="dropdown">
											<a class="nav-link dropdown-toggle" data-toggle="dropdown"