Skip to content
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

helm-operator when creating certificate via secret , diff certificate seen in different pods even after using same certificate from secret #6806

Open
malli31 opened this issue Aug 8, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@malli31
Copy link

malli31 commented Aug 8, 2024

Bug Report

helm-operator when creating certificate via secret , diff certificate seen in different pods even after using same certificate from secret

What did you do?

Created certificate in

{{- $cn := "localhost" }}

{{- $CA := genCA $cn 3650 }}
{{- $Cert := genSignedCert $cn nil nil 3650 $CA }}

{{- $PemCert := $Cert.Cert | b64enc | quote }}
{{- $PemKey := $Cert.Key | b64enc | quote }}
{{- $PemCA := $CA.Cert | b64enc | quote }}

apiVersion: v1
kind: Secret
metadata:
namespace: {{ .Release.Namespace }}
name: Secret-certs
data:
ca-cert.pem: {{ $PemCA }}

Started using this after mounting in my pods

volumes:
- name: container-certs
secret:
secretName: Secret-certs

What did you expect to see?

I want to have same certificate in both pods since same secret is being used

What did you see instead? Under which circumstances?

Environment

Operator type:

Kubernetes cluster type:

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants