OTA-1166: describe manifests

[hongkailiu]

No description provided.

[openshift-ci-robot]

@hongkailiu: This pull request references OTA-1166 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

[hongkailiu]

https://issues.redhat.com/browse/OTA-1166

[hongkailiu]

/retest-required

[wking]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, wking

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 [wking]

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

[hongkailiu]

/hold

Testing a bit with cluster bot + PR ...

[hongkailiu]

/retest-required

[hongkailiu]

/retest-required

[openshift-ci]

@hongkailiu: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[hongkailiu]

Verify with a cluster-bot cluster: The results look reasonable to me.

launch 4.16,openshift/cincinnati-operator#185 aws

and

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get ClusterServiceVersion update-service-operator.v5.0.2-dev -o yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
"This OpenShift Update Service operator Deployment reconciles local UpdateServices\
  \ into more fundamental Kubernetes\nand OpenShift resources like Cincinnati Deployments\
  \ and Routes, and it reports the status of those components in \nthe UpdateService\
  \ status.\n"

## This should be related to how the deployment is installed on the cluster (it may differs from how OLM handes CSV)
$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get deployment updateservice-operator -o yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
null

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get pdb sample -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
This PodDisruptionBudget blocks graceful evictions (but cannot guard against all external
  disruption) to try and keep at least one Pod running at all times, if the Update
  Service instance specifies two or more replicas.

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get svc sample-graph-builder -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
This Service exposes a client-agnostic update graph to other clients within the cluster.
  This allows convenient in-cluster access to those graphs, and also allows platform
  monitoring to scrape graph-builder containers for Prometheus metrics. See https://github.com/openshift/cincinnati/blob/master/docs/design/cincinnati.md#graph-builder
  for more details

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get svc sample-metadata -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
It exposes release image signatures See https://github.com/openshift/cincinnati-graph-data?tab=readme-ov-file#signatures
  for more details

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get svc sample-policy-engine -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
It exposes views of the update graph by applying a set of filters which are defined
  within the particular Policy Engine instance. See https://github.com/openshift/cincinnati/blob/master/docs/design/cincinnati.md#policy-engine
  for more details


$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get route sample-route -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
It exposes views of the update graph by applying a set of filters which are defined
  within the particular Policy Engine instance. See https://github.com/openshift/cincinnati/blob/master/docs/design/cincinnati.md#policy-engine
  for more details

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get route sample-meta-route -o  yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
It exposes release image signatures See https://github.com/openshift/cincinnati-graph-data?tab=readme-ov-file#signatures
  for more details

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get cm sample-config -o yaml |  yq -y '.metadata.annotations."kubernetes.io/description"'
This ConfigMap contains the configuration file for the graph-builder

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get cm sample-env -o yaml |  yq -y '.metadata.annotations."kubernetes.io/description"'
This ConfigMap contains the environment information shared by the containers of UpdateService

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get deployment sample -o yaml | yq -y '.metadata.annotations."kubernetes.io/description"'
This deployment launches the components for the OpenShift UpdateService sample

$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get secret sample-pull-secret -o yaml |  yq -y '.metadata.annotations."kubernetes.io/description"'
It contains the pull credentials from the global pull secret for the cluster

### Maybe it is not created by default
$ oc --kubeconfig ~/Downloads/cluster-bot-2024-07-08-204156.kubeconfig.txt -n install-osus-here get cm | grep trusted-ca

[hongkailiu]

/hold cancel