-
Notifications
You must be signed in to change notification settings - Fork 88
Extra certificates test #2243
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
base: development/2.12
Are you sure you want to change the base?
Extra certificates test #2243
Conversation
Hello sylvainsenechal,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
.github/workflows/end2end.yaml
Outdated
AZURE_BACKEND_ENDPOINT: http://devstoreaccount1.blob.azure-mock.zenko.local | ||
AZURE_BACKEND_QUEUE_ENDPOINT: http://devstoreaccount1.queue.azure-mock.zenko.local | ||
AZURE_BACKEND_ENDPOINT: https://devstoreaccount1.blob.azure-mock.zenko.local | ||
AZURE_BACKEND_QUEUE_ENDPOINT: https://devstoreaccount1.queue.azure-mock.zenko.local | ||
AZURE_SECRET_KEY: Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw== | ||
AWS_ENDPOINT: http://aws-mock.zenko.local |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should also use TLS for:
- AWS mock
- Mock S3C/metadata (used by ingestion)
- Mock DMF
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works with Azure/Aws.
For dmf/s3c, Added https://scality.atlassian.net/jira/software/c/projects/OS/boards/268?selectedIssue=ZENKO-5055
4e8fe43
to
8de3b5a
Compare
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
c9d273c
to
213f333
Compare
# certificates issued by our ClusterIssuer. cert-manager keeps secrets in its own namespace, | ||
# so we copy it to the default namespace where zenko-operator will be able to read it. | ||
kubectl get secret root-ca -n cert-manager -o yaml | | ||
sed 's/namespace: cert-manager/namespace: default/' | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be done with kubectl apply -n default -f -
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried but actually if we do this we have an error because there is a mismatch between the namespace in the yaml metadata and the specific namespace.
the namespace from the provided object "cert-manager" does not match the namespace "default"
213f333
to
4837ec7
Compare
4837ec7
to
2fc6a08
Compare
Issue : ZENKO-4544