Skip to content

Conversation

@sallyom
Copy link
Contributor

@sallyom sallyom commented Jan 11, 2019

@enj @evb changed the import paths here, too
cluster-osin-operator to cluster-authentication-operator
and using the naming conventions laid out by @deads2k in email thread:

ClusterOperator name  "authentication" - see note below
Operator Namespace “openshift-authentication-operator”   - this PR
Operator Deployment “cluster-authentication-operator”  - this PR
Operator Git repo “openshift/cluster-authentication-operator”  - will be changed
Operand Namespace “openshift-authentication” - this PR

*note: - in this PR it's "cluster-authentication-operator". There isn't consistency with that
name in clusters today, although going with majoritiy it would be "openshift-authentication-operator"

@openshift-ci-robot openshift-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 11, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from ad9c844 to 1ad5727 Compare January 13, 2019 17:19
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 13, 2019
@sallyom sallyom changed the title WIP replace cluster-osin-operator/cluster-authentication-operator replace cluster-osin-operator/cluster-authentication-operator Jan 13, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 13, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch 3 times, most recently from 2b9d8d7 to 6e7ab78 Compare January 14, 2019 20:34
@sallyom sallyom changed the title replace cluster-osin-operator/cluster-authentication-operator rename cluster-osin-operator/cluster-authentication-operator Jan 14, 2019
@ericavonb
Copy link
Contributor

@sallyom want to rebase? let's get this thing merged!

@sallyom sallyom force-pushed the cluster-osin-to-authentication branch 2 times, most recently from 2d7b082 to bc86875 Compare January 15, 2019 21:13
func defaultLabels() map[string]string {
return map[string]string{
"app": "origin-cluster-osin-operator2",
"app": "origin-cluster-authentication-operator2",
Copy link
Contributor

Choose a reason for hiding this comment

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

we don't need the 2

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done, fixed


const (
targetName = "openshift-osin" // TODO fix
targetName = "openshift-integrated-auth"
Copy link
Contributor

Choose a reason for hiding this comment

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

can you outline the new name requirements so we know if this matches

Copy link
Contributor Author

@sallyom sallyom Jan 16, 2019

Choose a reason for hiding this comment

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

from email thread (kube-apiserver example), naming conventions from @deads2k are as follows:

ClusterOperator name  "authentication" 
Operator Namespace “openshift-authentication-operator”  
Operator Deployment “cluster-authentication-operator”
Operator Git repo “openshift/cluster-authentication-operator”
Operand Namespace “openshift-authentication” -edited targetName above to match

componentNamespace = "openshift-authentication-operator"
)

func NewOperator() *cobra.Command {
Copy link
Contributor

Choose a reason for hiding this comment

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

cmd.User needs fixing

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've changed to operator

const (
componentName = "cluster-osin-operator2"
componentNamespace = "openshift-core-operators"
componentName = "cluster-authentication-operator2"
Copy link
Contributor

Choose a reason for hiding this comment

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

drop 2

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

componentName = "cluster-osin-operator2"
componentNamespace = "openshift-core-operators"
componentName = "cluster-authentication-operator2"
componentNamespace = "openshift-authentication-operator"
Copy link
Contributor

Choose a reason for hiding this comment

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

cite requirements

Copy link
Contributor Author

@sallyom sallyom Jan 16, 2019

Choose a reason for hiding this comment

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

from email thread:

ClusterOperator name  "authentication" 
Operator Deployment “cluster-authentication-operator”
Operator Namespace “openshift-authentication-operator” 

so, componentName should be "authentication" above according to email? However, looking at a cluster, most operators have the name "openshift-something-operator" and a few have "cluster-something-operator". I'm keeping with cluster-authentication-operator unless I hear otherwise, keeping with minimal change here.

const (
componentName = "cluster-osin-operator"
componentNamespace = "openshift-core-operators"
componentName = "cluster-authentication-operator"
Copy link
Contributor

Choose a reason for hiding this comment

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

do not touch anything in pkg/operator

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, done

metadata:
namespace: openshift-core-operators
name: origin-cluster-osin-operator
namespace: openshift-authentication-operator
Copy link
Contributor

Choose a reason for hiding this comment

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

do not mess with the original operator, we have no tests

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, done

image: quay.io/openshift/origin-cluster-authentication-operator:latest
imagePullPolicy: IfNotPresent
command: ["osin-operator", "operator"]
command: ["authentication-operator", "operator"]
Copy link
Contributor

Choose a reason for hiding this comment

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

this is the only line I expect to change

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

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 for both deployments, should be same, right?
command: ["authentication-operator", "operator"] (also in pkg/cmd/operator|operator2/cmd.go, same cmd.User for both? operator?)

metadata:
namespace: openshift-core-operators
name: origin-cluster-osin-operator2
namespace: openshift-authentication-operator
Copy link
Contributor

Choose a reason for hiding this comment

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

lots of 2's that need to die

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed them

@enj
Copy link
Contributor

enj commented Jan 15, 2019

I do not think the risk of breaking operator1 is worth it, so I do no think we should touch the old operator at all. At the bare minimum openshift/origin#21733 needs to be merged before this.

@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from bc86875 to bc05398 Compare January 15, 2019 23:28
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 15, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from bc05398 to 76436e7 Compare January 15, 2019 23:39
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 15, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from 76436e7 to e335abb Compare January 16, 2019 00:11
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 16, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch 3 times, most recently from 4213a55 to 09cff91 Compare January 16, 2019 19:00
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from 09cff91 to 1ac9642 Compare January 16, 2019 19:11
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 16, 2019
Copy link
Contributor

@ericavonb ericavonb left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 16, 2019
@sallyom
Copy link
Contributor Author

sallyom commented Jan 16, 2019

/hold cancel

@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 Jan 16, 2019
@sallyom
Copy link
Contributor Author

sallyom commented Jan 16, 2019

/hold
I'll rebase after other open PRs merge/unhold after

@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 Jan 16, 2019
@enj
Copy link
Contributor

enj commented Jan 17, 2019

/refresh

@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from 1ac9642 to d94b8c0 Compare January 17, 2019 17:16
@openshift-ci-robot
Copy link
Contributor

New changes are detected. LGTM label has been removed.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ericavonb, sallyom

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 size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 17, 2019
@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from 3b2bede to 70125ad Compare January 18, 2019 13:18
@petr-muller
Copy link
Member

/refresh

@sallyom
Copy link
Contributor Author

sallyom commented Jan 18, 2019

/retest

@sallyom sallyom force-pushed the cluster-osin-to-authentication branch from 70125ad to da42a7e Compare January 21, 2019 14:40
@enj
Copy link
Contributor

enj commented Jan 21, 2019

#34

@enj enj closed this Jan 21, 2019
@openshift-ci-robot
Copy link
Contributor

@sallyom: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws da42a7e link /test e2e-aws
ci/prow/e2e-aws-operator da42a7e link /test e2e-aws-operator

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants