-
Notifications
You must be signed in to change notification settings - Fork 172
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
reintroduce postgres operator example database pods #233
Conversation
6fdd42c
to
09e89f3
Compare
Do you happen to know around which commit this yaml was removed in? I'm curious if it was an accident or if we were trying to do something different/specific that didn't work the way we expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Clean up the warning in the readme saying this example doesn't work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@YrrepNoj looks like they were removed with commit f96ae20 / #144
Will do
@RothAndrew That's weird. They were coming up fine without it on my end. Let's take a look at it together when you have some time but try the new changes in the meantime. |
@wadedesir still getting ImagePullBackOff. See this github issue. Not sure why you aren't getting it. Are you using the vagrantfile that modifies the hosts file of the VM? If you aren't then it will just pull directly from the upstream registry and won't need authorization for the internal zarf docker registry. |
@RothAndrew @YrrepNoj Everything should be working as expected now. |
Screenshot coming in from @wadedesir. Through debugging it sounds like you can't configure imagePullSecrets or a different service account for the pooler pod, but we found this github issue that talks about patching the default serviceaccount in that namespace. I recommended that we do that same thing but as a |
|
/test all |
Signed-off-by: Jeff McCoy <[email protected]>
Signed-off-by: Jeff McCoy <[email protected]>
Should fix #201 It appears the postgres-cluster yaml was not present in the newer versions of this example and thus the database pods were not being created accordingly.