-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
area/helmImpacts helm charts and user deployment experienceImpacts helm charts and user deployment experiencekind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
helm install cilium cilium/cilium \
--version 1.11.5 \
--namespace kube-system \
--set ipam.mode=kubernetes \
--set kubeProxyReplacement=strict \
--set k8sServiceHost=10.111.111.13 \
--set k8sServicePort=6443 \
--set ipMasqAgent.enabled=true \
--set hostServices.enabled=true \
--set installIptablesRules=false \
--set loadBalancer.mode=dsr \
--set l7Proxy=false \
--set cgroup.autoMount.enabled=false \
--set cgroup.hostRoot=/sys/fs/cgroup \
--set enableIPv4Masquerade=true
After this warnings came up about depreciated and non-functional options.
Cilium Version
1.11.5.
Kernel Version
5.15.0-33-generic
Kubernetes Version
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6+k3s1", GitCommit:"418c3fa858b69b12b9cefbcff0526f666a6236b9", GitTreeState:"clean", BuildDate:"2022-04-28T22:16:18Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
cilium-sysdump-20220527-104811.zip
Relevant log output
W0527 10:45:23.073316 13910 warnings.go:70] spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].key: beta.kubernetes.io/os is deprecated since v1.14; use "kubernetes.io/os" instead
W0527 10:45:23.073384 13910 warnings.go:70] spec.template.metadata.annotations[scheduler.alpha.kubernetes.io/critical-pod]: non-functional in v1.16+; use the "priorityClassName" field instead
NAME: cilium
LAST DEPLOYED: Fri May 27 10:45:17 2022
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
You have successfully installed Cilium with Hubble.
Your release version is 1.11.5.
For any further help, visit https://docs.cilium.io/en/v1.11/gettinghelp
Anything else?
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
area/helmImpacts helm charts and user deployment experienceImpacts helm charts and user deployment experiencekind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.