Skip to content

Conversation

@guillaumerose
Copy link
Contributor

This implements phase 1 of openshift/enhancements#482

@rkukura
Copy link

rkukura commented Nov 30, 2020

Do the manifests under vendor/github.com/openshift/api also need to be updated to pickup the profile annotations?

@stlaz
Copy link
Contributor

stlaz commented Dec 1, 2020

Please explain in details of what the annotation actually does in the commit message, link to an enhancement won't do for anyone who wants to quickly understand why the annotation's there.

I haven't read the enhancement and I do not know the consequences of this annotation. Single-node cluster sounds contradictive. Does that mean the operator's code will need to change? Who is going to implement the necessary changes?

@stlaz
Copy link
Contributor

stlaz commented Dec 1, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 1, 2020
This partially implements phase 1 of openshift/enhancements#482 and
does not change behavior. Initially, all manifests are included in
the single-node-developer cluster profile. Follow-on PRs may exclude
any of these that are not needed in the profile.
@guillaumerose
Copy link
Contributor Author

I updated the commit message.

In a future release, cluster profile will be used to determine which manifests will be applied by the CVO. The default profile is self-managed-high-availability.
CRC will use a new one, single-node-developer and edge production cluster single-node-production.

Does that mean the operator's code will need to change?

Yes. Right now, we don't modify operators but in the future we might have to open PRs to fine tune operators for our profile.
For this operator, a good thing for us would be to customize https://github.com/openshift/cluster-authentication-operator/blob/master/manifests/02_config.cr.yaml and directly include useUnsupportedUnsafeNonHANonProductionUnstableOAuthServer.

Who is going to implement the necessary changes?

Teams that need it. For the single-node-developer profile, CRC team.

@stlaz
Copy link
Contributor

stlaz commented Dec 2, 2020

/hold cancel

Who is going to implement the necessary changes?

Teams that need it. For the single-node-developer profile, CRC team.

I'm taking your word for it, then ;)

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 2, 2020
@stlaz
Copy link
Contributor

stlaz commented Dec 2, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guillaumerose, stlaz

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

The pull request process is described here

Details 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 Dec 2, 2020
@openshift-bot
Copy link
Contributor

/retest

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

13 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.

@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.

@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.

4 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.

@cfergeau
Copy link

cfergeau commented Dec 3, 2020

I don't think the CI failures are related to this PR? Are there ongoing issues with CI?

@openshift-merge-robot openshift-merge-robot merged commit 210fab8 into openshift:master Dec 3, 2020
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.

7 participants