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

Add pull secret management for DTK #110

Merged
merged 3 commits into from
Oct 14, 2021

Conversation

pacevedom
Copy link
Collaborator

When deploying in GCP the crane package gets into an infinite loop if traffic towards metadata server is dropped. This makes SRO unresponsive.
Changing authn discovery from crane package into a manual approach where we grab the pull secrets from a secret will avoid the use of the metadata server while still being able to authenticate and obtain the same info.

Signed-off-by: Pablo Acevedo Montserrat pacevedo@redhat.com

pkg/registry/registry.go Outdated Show resolved Hide resolved
@SchSeba
Copy link

SchSeba commented Oct 11, 2021

Hi @pacevedom quick question why do you need to create an empty folder in the pod definition?

@pacevedom
Copy link
Collaborator Author

pacevedom commented Oct 11, 2021

@SchSeba the crane package will look for existing credentials (if not configured otherwise, but this was the source of the issue in the first place) in $HOME/.docker/config.json. Since the pod is using a read-only root file system we need to create that dir so that its writable, hence the memory-backed volume.

@SchSeba
Copy link

SchSeba commented Oct 11, 2021

Oh sorry I miss that the pod file system is RO.

Thanks!
/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2021

@SchSeba: changing LGTM is restricted to collaborators

In response to this:

Oh sorry I miss that the pod file system is RO.

Thanks!
/lgtm

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.

Copy link

@SchSeba SchSeba left a comment

Choose a reason for hiding this comment

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

2 small comments

pkg/registry/registry.go Outdated Show resolved Hide resolved
pkg/registry/registry.go Outdated Show resolved Hide resolved
Copy link

@SchSeba SchSeba left a comment

Choose a reason for hiding this comment

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

great just remove the duplicate variable and this PR is ready from my point of view

pkg/registry/registry.go Outdated Show resolved Hide resolved
Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>
Copy link

@SchSeba SchSeba left a comment

Choose a reason for hiding this comment

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

lgtm

@dagrayvid
Copy link
Collaborator

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Oct 13, 2021
@dagrayvid dagrayvid removed the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Oct 14, 2021
@dagrayvid
Copy link
Collaborator

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Oct 14, 2021
@SchSeba
Copy link

SchSeba commented Oct 14, 2021

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Oct 14, 2021

@SchSeba: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@dagrayvid
Copy link
Collaborator

/approve

@openshift-ci
Copy link

openshift-ci bot commented Oct 14, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dagrayvid, pacevedom

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 14, 2021
@bthurber
Copy link
Collaborator

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2021
@openshift-merge-robot openshift-merge-robot merged commit b1a21cb into openshift-psap:master Oct 14, 2021
pacevedom added a commit to pacevedom/special-resource-operator that referenced this pull request Oct 14, 2021
* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9
pacevedom added a commit to pacevedom/special-resource-operator that referenced this pull request Oct 14, 2021
* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>
pacevedom added a commit to pacevedom/special-resource-operator that referenced this pull request Oct 14, 2021
* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9
openshift-merge-robot pushed a commit that referenced this pull request Oct 15, 2021
* Add pull secret management for DTK (#110)

* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9

* Update OSMajor and OSMajorMinor when multiple kernel versions are running in cluster. Refer issue 93 for more details. (#109)

Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>

Co-authored-by: Veritas Technologies LLC <opensource@veritas.com>
Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>
ybettan pushed a commit to ybettan/special-resource-operator that referenced this pull request Nov 2, 2021
…eploy simple-kmod on GCP (openshift-psap#61)

* Add pull secret management for DTK (openshift-psap#110)

* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Update OSMajor and OSMajorMinor when multiple kernel versions are running in cluster. Refer issue 93 for more details. (openshift-psap#109)

Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>

Co-authored-by: Pablo Acevedo Montserrat <pabloacevedom@gmail.com>
Co-authored-by: Veritas Technologies LLC <opensource@veritas.com>
Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>
ybettan pushed a commit to ybettan/special-resource-operator that referenced this pull request Nov 2, 2021
…mod on GCP (openshift-psap#58)

* Add pull secret management for DTK (openshift-psap#110)

* Add pull secret management

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Adjust vendor dependencies

* Update bundle for 4.9

Signed-off-by: Pablo Acevedo Montserrat <pacevedo@redhat.com>

* Update OSMajor and OSMajorMinor when multiple kernel versions are running in cluster. Refer issue 93 for more details. (openshift-psap#109)

Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>

Co-authored-by: Veritas Technologies LLC <opensource@veritas.com>
Co-authored-by: Reena Kabra <Reena.Kabra@veritas.com>
yevgeny-shnaidman added a commit to yevgeny-shnaidman/special-resource-operator that referenced this pull request Feb 21, 2022
…t-psap#110)

This PR removes processing of the stateless yaml from the statefull
yamls state machine loop. The fixed flow is:
1) split the original chart's templates to statefull, stateless and named templates
2) first run named templates with each statefull yaml ( in order)
3) run named templates with all the stateless yaml togetter
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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants