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

set packageserver replicas to 1 for single node #2062

Conversation

ankitathomas
Copy link
Contributor

The single-node topology should allow only a single instance of the package server. The 1 replica default was to avoid fatal discovery errors for the packageserver api, which have been updated to non-fatal errors as of kubernetes/kubernetes#73035.

Reverting the default packageserver replicas to 1

@kevinrizza
Copy link
Member

/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, kevinrizza

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 30, 2021
@ankitathomas
Copy link
Contributor Author

/retest

@@ -70,7 +70,7 @@ spec:
spec:
strategy:
type: RollingUpdate
replicas: 2
replicas: 1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, we probably don't want to update this existing released manifest. It'll just get updated in the next release.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, the same goes for the change to deploy/ocp/manifests/0.17.0/0000_50_olm_15-packageserver.clusterserviceversion.yaml.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I've reverted the changes on the released manifests. The quickstart manifest is still using single replica packageserver.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, hold on, I think we do need this change to land in the downstream manifests/ directory (unless we want to only make that change in the downstream repo?), we just don't want it to land in any of the /0.17.0 release directories because those releases are already, well, released.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we want to update replicas in the ocp manifests then?

@ankitathomas ankitathomas force-pushed the single-node-packageserver branch 2 times, most recently from 4a59638 to 32d5ba1 Compare April 1, 2021 15:13
Signed-off-by: Ankita Thomas <ankithom@redhat.com>
@ankitathomas
Copy link
Contributor Author

/retest

@benluddy
Copy link
Contributor

benluddy commented Apr 1, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 1, 2021
@kevinrizza
Copy link
Member

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants