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

secrets syncing is not proper #233

r-divakaran-hrs opened this issue Mar 3, 2018 · 2 comments


None yet
4 participants
Copy link

commented Mar 3, 2018


I was trying to set up kubed, for a cluster. Installed using helm as below

helm install stable/kubed --name kubed 

Then created a secret, using below file

apiVersion: v1
kind: Secret
  name: image-pull-secret
  annotations: ""
  .dockerconfigjson: xxxxxxxxxxxxxxxxxxx-====---=xkjxxcoxox--==

Once the secret is created am trying to install one of our service using helm in another namespace called kube-p, but its not working as its not able to download the docker image from our registry. As the above secret is supposed to be used.
One thing I noticed is that the secret I created is of type, but when they are synced by kubed to other namespaces they are of type opaque.

default        image-pull-secret                1         1m
kube-x   image-pull-secret                  Opaque                                1         1m
kube-y    image-pull-secret                  Opaque                                1         1m
kube-system    image-pull-secret                  Opaque                                1         1m
kube-z     image-pull-secret                  Opaque                                1         1m
kube-p        image-pull-secret                  Opaque                                1         1m

Is that an expected behaviour !?

I am suspecting its an issue with kubed coz, when I create the secret without appscode annotation separately to each namespace, things are working as expected.


@tamalsaha tamalsaha added this to the 0.6.0 milestone Mar 16, 2018


This comment has been minimized.

Copy link

commented May 29, 2018

Should be fixed by release. Please reopen if you are still having this issue.

@tamalsaha tamalsaha closed this May 29, 2018

@tamalsaha tamalsaha modified the milestones: 0.6.0, 0.7.0 May 29, 2018

@tamalsaha tamalsaha assigned hossainemruz and unassigned diptadas May 29, 2018

@tamalsaha tamalsaha reopened this May 29, 2018


This comment has been minimized.

Copy link

commented May 29, 2018

Need to also copy type

obj.Data = src.Data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.