You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the usage instructions with a few modifications because my K3S is accessible as root user as installed:
$ sudo helm repo add mittwald https://helm.mittwald.de
"mittwald" already exists with the same configuration, skipping
$ sudo helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "mittwald" chart repository
Update Complete. ⎈Happy Helming!⎈
$ sudo helm upgrade --kubeconfig /etc/rancher/k3s/k3s.yaml --install kubernetes-secret-generator mittwald/kubernetes-secret-generator
Release "kubernetes-secret-generator" does not exist. Installing it now.
NAME: kubernetes-secret-generator
LAST DEPLOYED: Wed Jun 1 07:45:07 2022
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
$ cat mysecret.yaml
apiVersion: v1
kind: Secret
metadata:
name: mysecret
annotations:
secret-generator.v1.mittwald.de/type: string
secret-generator.v1.mittwald.de/autogenerate: password
#spec:
# forceRegenerate: false
data:
username: UGxlYXNlQWNjZXB0Cg==
$ sudo kubectl apply -f mysecret.yaml
secret/mysecret created
$ sudo kubectl describe secret mysecret
Name: mysecret
Namespace: default
Labels: <none>
Annotations: secret-generator.v1.mittwald.de/autogenerate: password
secret-generator.v1.mittwald.de/type: string
Type: Opaque
Data
====
username: 13 bytes
$ sudo kubectl get secret mysecret -o jsonpath='{.data}'
{"username":"UGxlYXNlQWNjZXB0Cg=="}
From above output, it appears the secret only contains the predefined element "username" and that the password is not generated. Further, if I uncomment a couple of lines from mysecret.yaml, it complains:
$ sudo kubectl apply -f mysecret.yaml
error: error validating "mysecret.yaml": error validating data: ValidationError(Secret): unknown field "spec" in io.k8s.api.core.v1.Secret; if you choose to ignore these errors, turn validation off with --validate=false
Then I noticed the pod failing:
$ sudo kubectl get pods -n default
NAME READY STATUS RESTARTS AGE
kubernetes-secret-generator-9b7946ff5-znxfz 0/1 CrashLoopBackOff 5 (88s ago) 5m15s
$ sudo kubectl logs kubernetes-secret-generator-9b7946ff5-znxfz
standard_init_linux.go:228: exec user process caused: exec format error
From what I can see, the underlying image is for x84_64 architecture. Can we have one for ARM64?
The text was updated successfully, but these errors were encountered:
anon-software
changed the title
The secrets are not generated on K3S
The secrets are not generated on Raspberry PI cluster
Jun 1, 2022
There has not been any activity to this issue in the last 30 days. It will automatically be closed after 7 more days. Remove the stale label to prevent this.
I followed the usage instructions with a few modifications because my K3S is accessible as root user as installed:
From above output, it appears the secret only contains the predefined element "username" and that the password is not generated. Further, if I uncomment a couple of lines from mysecret.yaml, it complains:
Then I noticed the pod failing:
From what I can see, the underlying image is for x84_64 architecture. Can we have one for ARM64?
The text was updated successfully, but these errors were encountered: