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

K8SPG-604: fix custom-extensions for non 16 PG version #912

Merged
merged 2 commits into from
Sep 26, 2024

Conversation

eleo007
Copy link
Contributor

@eleo007 eleo007 commented Sep 26, 2024

K8SPG-604 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:
Custom-extensions test fails when not PG 16 version is used

Cause:
initContainers.name in tests contains PG16 version hardcoded.

Solution:
Remove entries from tests that have hardcoded version

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PG version?
  • Does the change support oldest and newest supported Kubernetes version?

@hors hors merged commit 9ba68fb into release-2.5.0 Sep 26, 2024
14 of 17 checks passed
@hors hors deleted the K8SPG-604-custom-extensions branch September 26, 2024 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants