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

RHTAPINST-49: OpenShift Pipelines Configuration #44

Merged
merged 2 commits into from
Jun 25, 2024

Conversation

otaviof
Copy link
Collaborator

@otaviof otaviof commented Jun 24, 2024

Moving the Tekton Chains configuration to the infrastructure chart, replacing the pre-deploy hook with a post-deploy job that will create the Tekton Chains resources.

Improved the Helm chart testing to wait for OpenShift Pipelines to be ready, and using official Chainguard images to run cosign.

After #43 and #42 🙏

@@ -0,0 +1,28 @@
{{- if .Values.infrastructure.openShiftPipelines.enabled }}
Copy link
Member

Choose a reason for hiding this comment

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

This resource feels superfluous.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That's the link with RHDH toggle. So, when RHDH is disabled we can also disable OpenShift Pipelines changes.

# Labels to add to the resource.
labels: {}
# Tekton Chains settings.
tektonChains:
Copy link
Member

Choose a reason for hiding this comment

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

This section can go away, I don't see it's value.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That section controls Tekton Chains related settings, and replaces hook scripts. In fact, is quite relevant.

Copy link
Member

Choose a reason for hiding this comment

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

I don't think any of these values are controlled by the user.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

These attributes have defaults, they should be good enough to work with the current version of OpenShift Pipelines, and allow us to modify as we move forward. The entries added to the values.yaml are, in fact, variables that we use in multiple resources to avoid duplication, among other reasons to define them.

Additionally, by having these attributes we can leverage their relationship via values.yaml.tpl.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

For the record, I moved the defaults to the values.yaml on rhtap-infrastructure instead of setting them up on values.yaml.tpl.

Copy link
Member

@Roming22 Roming22 left a comment

Choose a reason for hiding this comment

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

Please rebase to simplify the review.

# Labels to add to the resource.
labels: {}
# Tekton Chains settings.
tektonChains:
Copy link
Member

Choose a reason for hiding this comment

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

I don't think any of these values are controlled by the user.

meta.helm.sh/release-namespace: {{ $argoCDNamespace }}
labels:
app.kubernetes.io/managed-by: Helm
tektonChains:
Copy link
Member

Choose a reason for hiding this comment

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

Let's discuss tomorrow why that's needed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's needed to replace this:

make_helm_managed() {
KIND="$1"
NAMESPACE="$2"
NAME="$3"
echo -n "."
kubectl annotate "$KIND" "$NAME" meta.helm.sh/release-name=rhtap-backing-services >/dev/null
echo -n "."
kubectl annotate "$KIND" "$NAME" meta.helm.sh/release-namespace="$NAMESPACE" >/dev/null
echo -n "."
kubectl label "$KIND" "$NAME" app.kubernetes.io/managed-by=Helm >/dev/null
}

Thus we can run these type of interactions in the cluster, without the need for extra local tools to run rhtap-cli.

@konflux-ci-qe-bot
Copy link

@otaviof: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
rhtap-cli-nt6jt-g6jz8 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:rhtap-cli-nt6jt-g6jz8

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@otaviof
Copy link
Collaborator Author

otaviof commented Jun 24, 2024

Please rebase to simplify the review.

Sure! Just rebased, please consider.

@otaviof otaviof force-pushed the RHTAPINST-49 branch 2 times, most recently from 5dd954d to 0b596a0 Compare June 24, 2024 15:14
@konflux-ci-qe-bot
Copy link

@otaviof: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
rhtap-cli-zkzkj-bzkgz /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:rhtap-cli-zkzkj-bzkgz

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@otaviof otaviof requested a review from Roming22 June 25, 2024 04:13
Moving the Tekton Chains configuration to the infrastructure chart,
replacing the pre-deploy hook with a post-deploy job that will create
the Tekton Chains resources.

Improved the Helm chart testing to wait for OpenShift Pipelines to be
ready, and using official Chainguard images to run `cosign.`
@Roming22 Roming22 merged commit 753598d into redhat-appstudio:main Jun 25, 2024
1 check passed
@konflux-ci-qe-bot
Copy link

@otaviof: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
rhtap-cli-qrvrp-zfdf6 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:rhtap-cli-qrvrp-zfdf6

For instructions on how to install ORAS, please refer to the ORAS installation guide.

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

Successfully merging this pull request may close these issues.

3 participants