-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs: update GKE ambient guide to remove manual ResourceQuota step (Fix istio/istio#56376) #16660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
parv18050212
wants to merge
11
commits into
istio:master
Choose a base branch
from
parv18050212:fix/gke-resourcequota-56376
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+22
−27
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
4bc4815
docs: update GKE ambient guide to remove manual ResourceQuota step (F…
parv18050212 26baa00
Update content/en/docs/ambient/install/platform-prerequisites/index.md
parv18050212 bd30dac
Update content/en/docs/ambient/install/platform-prerequisites/index.md
parv18050212 65bd2df
Update content/en/docs/ambient/install/platform-prerequisites/index.md
parv18050212 4a9b3a6
Merge branch 'istio:master' into fix/gke-resourcequota-56376
parv18050212 911fa08
docs: move GKE Namespace restrictions below Platform profile
parv18050212 12cedb2
final updated
parv18050212 7cb276f
fixed lint error
parv18050212 8dd2737
docs: corrected lint issues
parv18050212 cbf32dc
docs: fix code block formatting for lint compliance in GKE section
parv18050212 cb82172
docs: prepend $ to bash code blocks to fix Hugo lint errors
parv18050212 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,12 +17,29 @@ Certain Kubernetes environments require you to set various Istio configuration o | |
|
||
### Google Kubernetes Engine (GKE) | ||
|
||
#### Platform profile | ||
|
||
When using GKE you must append the correct `platform` value to your installation commands, as GKE uses nonstandard locations for CNI binaries which requires Helm overrides. | ||
|
||
#### istioctl ambient | ||
|
||
{{< text syntax=bash >}} | ||
$ istioctl install --set profile=ambient --set values.cni.platform=gke | ||
{{< /text >}} | ||
|
||
#### Helm ambient | ||
|
||
{{< text syntax=bash >}} | ||
$ helm install istio-cni charts/cni --set profile=ambient --set values.cni.platform=gke | ||
{{< /text >}} | ||
|
||
#### Namespace restrictions | ||
|
||
On GKE, any pods with the [system-node-critical](https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/) `priorityClassName` can only be installed in namespaces that have a [ResourceQuota](https://kubernetes.io/docs/concepts/policy/resource-quotas/) defined. By default in GKE, only `kube-system` has a defined ResourceQuota for the `node-critical` class. The Istio CNI node agent and `ztunnel` both require the `node-critical` class, and so in GKE, both components must either: | ||
On GKE, any pods with the [system-node-critical](https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/) `priorityClassName` can only be installed in namespaces that have a [ResourceQuota](https://kubernetes.io/docs/concepts/policy/resource-quotas/) defined. The Istio CNI node agent and `ztunnel` both require the `node-critical` class. | ||
|
||
By default in GKE, only `kube-system` has a defined ResourceQuota for the `node-critical` class. Installing Istio with the `ambient` profile creates a ResourceQuota in the `istio-system` namespace. | ||
|
||
- Be installed into `kube-system` (_not_ `istio-system`) | ||
- Be installed into another namespace (such as `istio-system`) in which a ResourceQuota has been manually created, for example: | ||
To install Istio in any other namespace, you must manually create a ResourceQuota: | ||
|
||
{{< text syntax=yaml >}} | ||
apiVersion: v1 | ||
|
@@ -41,30 +58,6 @@ spec: | |
- system-node-critical | ||
{{< /text >}} | ||
|
||
#### Platform profile | ||
|
||
When using GKE you must append the correct `platform` value to your installation commands, as GKE uses nonstandard locations for CNI binaries which requires Helm overrides. | ||
|
||
{{< tabset category-name="install-method" >}} | ||
|
||
{{< tab name="Helm" category-value="helm" >}} | ||
|
||
{{< text syntax=bash >}} | ||
$ helm install istio-cni istio/cni -n istio-system --set profile=ambient --set global.platform=gke --wait | ||
{{< /text >}} | ||
|
||
{{< /tab >}} | ||
|
||
{{< tab name="istioctl" category-value="istioctl" >}} | ||
|
||
{{< text syntax=bash >}} | ||
$ istioctl install --set profile=ambient --set values.global.platform=gke | ||
{{< /text >}} | ||
|
||
{{< /tab >}} | ||
|
||
{{< /tabset >}} | ||
|
||
### Amazon Elastic Kubernetes Service (EKS) | ||
|
||
If you are using EKS: | ||
|
@@ -265,7 +258,9 @@ The following configurations apply to all platforms, when certain {{< gloss "CNI | |
|
||
1. Cilium currently defaults to proactively deleting other CNI plugins and their config, and must be configured with | ||
`cni.exclusive = false` to properly support chaining. See [the Cilium documentation](https://docs.cilium.io/en/stable/helm-reference/) for more details. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are these newlines important? |
||
1. Cilium's BPF masquerading is currently disabled by default, and has issues with Istio's use of link-local IPs for Kubernetes health checking. Enabling BPF masquerading via `bpf.masquerade=true` is not currently supported, and results in non-functional pod health checks in Istio ambient. Cilium's default iptables masquerading implementation should continue to function correctly. | ||
|
||
1. Due to how Cilium manages node identity and internally allow-lists node-level health probes to pods, | ||
applying any default-DENY `NetworkPolicy` in a Cilium CNI install underlying Istio in ambient mode will cause `kubelet` health probes (which are by-default silently exempted from all policy enforcement by Cilium) to be blocked. This is because Istio uses a link-local SNAT address for kubelet health probes, which Cilium is not aware of, and Cilium does not have an option to exempt link-local addresses from policy enforcement. | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.