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

Sync entitlement secret #1050

Closed

Conversation

stuartwdouglas
Copy link
Contributor

No description provided.

@stuartwdouglas stuartwdouglas force-pushed the sync-entititlement-secret branch from bacbd47 to 569567f Compare June 3, 2024 07:47
@gbenhaim gbenhaim added the hold label Jun 3, 2024
@@ -189,6 +189,8 @@ spec:
fi

rsync -ra $(workspaces.source.path)/ "$SSH_HOST:$BUILD_DIR/workspaces/source/"
rsync -ra /entitlement/ "$SSH_HOST:$BUILD_DIR/volumes/etc-pki-entitlement/"
rsync -ra /mnt/trusted-ca/ "$SSH_HOST:$BUILD_DIR/volumes/trusted-ca/"
Copy link
Member

Choose a reason for hiding this comment

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

will it still work if /mnt/trusted-ca doesn't exist? mounting the configmap to that directory is optional and only happens with the configmap with the ca bundle is configured in the namespace.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, I forgot to respond to this. I tested it locally and it seemed to work fine.

Copy link
Member

Choose a reason for hiding this comment

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

thanks for checking

@gbenhaim gbenhaim removed the hold label Jun 6, 2024
@gbenhaim gbenhaim added this pull request to the merge queue Jun 6, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Jun 6, 2024
@gbenhaim
Copy link
Member

gbenhaim commented Jun 6, 2024

/test buildah-remote

@openshift-merge-robot
Copy link

PR needs rebase.

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-sigs/prow repository.

@gbenhaim
Copy link
Member

@stuartwdouglas why did you close this one? is there another pr for making those changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants