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

Bug 1788670: Use DNS for CatalogSource address #277

Conversation

kevinrizza
Copy link
Member

Problem:
Marketplace needs to support ipv6 clusters. Currently when creating
catalogsources, the marketplace points the catsrc to the clusterIP
address of the registry pod that it spins up. This cluster ip will not
work in an ipv6 only cluster.

Solution:
Use the dns address of the service to wire up the catalogsource to the
registry pod.

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 9, 2020
@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 9, 2020
@kevinrizza
Copy link
Member Author

/cc @njhale

@njhale
Copy link
Member

njhale commented Jan 10, 2020

/retest

5 similar comments
@njhale
Copy link
Member

njhale commented Jan 10, 2020

/retest

@kevinrizza
Copy link
Member Author

/retest

@kevinrizza
Copy link
Member Author

/retest

@kevinrizza
Copy link
Member Author

/retest

@ecordell
Copy link
Member

/retest

@@ -108,6 +112,19 @@ func (r *GrpcCatalog) EnsureResources(key types.NamespacedName, displayName, pub
return nil
}

func setTimestampLabel(catsrc *olm.CatalogSource) {
Copy link
Member

Choose a reason for hiding this comment

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

not 100% sure this is necessary, since we watch events on the GRPC connection and resync the catalogsource if the connection state changes.

The grpc connection can't live through a pod rollout but this seems like a reasonable safeguard in case some events are missed / issues with the grpc conection watch.

@ecordell
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2020
Problem:
Marketplace needs to support ipv6 clusters. Currently when creating
catalogsources, the marketplace points the catsrc to the clusterIP
address of the registry pod that it spins up. This cluster ip will not
work in an ipv6 only cluster.

Solution:
Use the dns address of the service to wire up the catalogsource to the
registry pod.
@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 13, 2020
@kevinrizza
Copy link
Member Author

/test e2e-aws-operator

Copy link
Member

@ecordell ecordell 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 the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ecordell, 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:
  • OWNERS [ecordell,kevinrizza]

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

@openshift-merge-robot openshift-merge-robot merged commit 9294890 into operator-framework:master Jan 13, 2020
@ecordell ecordell changed the title Use DNS for CatalogSource address Bug 1788670: Use DNS for CatalogSource address Jan 14, 2020
@openshift-ci-robot
Copy link
Contributor

@kevinrizza: All pull requests linked via external trackers have merged. Bugzilla bug 1788670 has been moved to the MODIFIED state.

In response to this:

Bug 1788670: Use DNS for CatalogSource address

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.

@ecordell
Copy link
Member

ecordell commented Mar 4, 2020

/cherry-pick release-4.3

@openshift-cherrypick-robot

@ecordell: new pull request created: #285

In response to this:

/cherry-pick release-4.3

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.

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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants