glamorous-australia-21342
04/04/2023, 3:50 PMcfg.requireSecret("secret1").apply(secret1=>{
cfg.requireSecret("secret2").apply(secret2=>{
const k8sSecret = new k8s.core.v1.Secret(`${k8sSecretName}-secret`, {
data: {
"access-id": secret1,
"secret-key": secret2,
},
},{ parent: k8sNamespace });
})
})
And getting the following error:
error: resource default/k8sSecretName-7e8f35be was not successfully created by the Kubernetes API server : Secret in version "v1" cannot be handled as a Secret: illegal base64 data at input byte 40
billowy-army-68599
04/04/2023, 3:51 PMstringData
glamorous-australia-21342
04/04/2023, 3:52 PMbillowy-army-68599
04/04/2023, 3:52 PMstringData
doesglamorous-australia-21342
04/04/2023, 3:52 PMdata
then?billowy-army-68599
04/04/2023, 3:56 PMglamorous-australia-21342
04/04/2023, 3:56 PMmany-telephone-49025
04/07/2023, 8:27 AMexternal-secrets
for Kubernetes secret management. Depending on where you run your k8s cluster you may have a managed service for that.able-crayon-21563
04/09/2023, 10:06 PMdata
. The stringData
field is provided for convenience, to have the API server perform the encoding for you. Same result.
https://kubernetes.io/docs/concepts/configuration/secret/#restriction-names-data