We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Backport fix for rke2-snapshot-validation-webhook fails to get endpoints while the pod returns ready
The text was updated successfully, but these errors were encountered:
Infrastructure Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
cat /etc/os-release ec2-user@ip-172-31-4-114:~> cat /etc/os-release NAME="SLES" VERSION="15-SP4" VERSION_ID="15.4" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP4"
Cluster Configuration: 3 server 1 agent
Config.yaml:
cat /etc/rancher/rke2/config,yaml write-kubeconfig-mode: "0644" tls-san: - fake.fqdn.value node-name: ip-172-31-4-114.us-east-2.compute.internal profile: cis-1.23 cni: calico
Validation results:
ec2-user@ip-172-31-4-219:~> rke2 -v rke2 version v1.28.7-rc3+rke2r1 (fe8538a165d25755050d2a0827dbf982f72611fa) go version go1.21.7 X:boringcrypto ec2-user@ip-172-31-4-219:~> kubectl get endpoints -n kube-system rke2-snapshot-validation-webhook NAME ENDPOINTS AGE rke2-snapshot-validation-webhook 10.42.201.203:8443 85m ec2-user@ip-172-31-4-219:~> kubectl create -f - <<EOF > apiVersion: snapshot.storage.k8s.io/v1 > kind: VolumeSnapshot > metadata: > name: bad-snapshot-demo > namespace: default > spec: > source: > persistentVolumeClaimName: csi-pvc > volumeSnapshotClassName: "" > EOF Error from server: error when creating "STDIN": admission webhook "rke2-snapshot-validation-webhook.csi.kubernetes.io" denied the request: Spec.VolumeSnapshotClassName must not be the empty string ec2-user@ip-172-31-4-219:~>
Sorry, something went wrong.
brandond
ShylajaDevadiga
No branches or pull requests
Backport fix for rke2-snapshot-validation-webhook fails to get endpoints while the pod returns ready
The text was updated successfully, but these errors were encountered: