Update PGO installer to 5.8.6#4373
Conversation
|
❓ Looks like the go-test failure is related to the CRD check failing. Do those need to be regenerated? |
The issue is that the CRDs we put in our official installer are slightly different from the "raw" CRDs we generate in the |
config/LICENSE.txt
Outdated
There was a problem hiding this comment.
❓ I'm a bit unclear as to what's happening with this license versus what we're doing with this one. Do we need both?
There was a problem hiding this comment.
The installer on main doesn't have this file but I do see it as a removed file from the examples repo. Maybe it should be added to main as well?
There was a problem hiding this comment.
🤔 As mentioned on the PR for main, assuming this license should be here, I think this update is good so I will approve. Might still be worth verifying though.
| resources: | ||
| - role_binding.yaml | ||
| - role.yaml | ||
| - service_account.yaml No newline at end of file |
| resources: | ||
| - ../cluster | ||
| components: | ||
| - ../../../components/single-namespace No newline at end of file |
dsessler7
force-pushed
the
update-installer-5.8.6
branch
from
b0c00fc to
3504a29
Compare
|
We only release one community installer for the latest version per release, and that is now 6.0, so we can close this. |
3 participants
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
Older installer before we moved the official installer to the postgres-operator repo
What is the new behavior (if this is a feature change)?
Latest installer with newer images and general installer structure.
Other Information: