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

api: Rename Payload to Image in ClusterVersion status #98

Merged
merged 5 commits into from Jan 24, 2019

Conversation

smarterclayton
Copy link
Contributor

The payload is delivered as an image, and we have clarified our terminology in multiple spots to say:

  • An update is delivered in an image
  • An image carrying an OpenShift update is a release image
  • A release image is associated with a version of the product
  • The contents of the release image include the CVO binary and an update payload
  • The update payload is a set of on disk manifests and associated metadata

This PR includes the openshift/api changes and reacts to those updates.

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 23, 2019
@smarterclayton
Copy link
Contributor Author

/test integration

@abhinavdahiya
Copy link
Contributor

both abd3ec0 and dd266e1 are both changing vendor/github.com/openshift/api/config/v1/types_cluster_version.go ;)

glog.V(3).Infof("ClusterOperator %s/%s is not done for version %s; it is version=%v, available=%v, progressing=%v, failing=%v",
eos.Namespace, eos.Name, os.Status.Version,
eos.Status.Version, available, progressing, failing)
glog.V(3).Infof("ClusterOperator %s/%s is not done for version %s; it is available=%v, progressing=%v, failing=%v",
Copy link
Contributor

Choose a reason for hiding this comment

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

version %s is extra

@@ -133,7 +133,12 @@ func (m *operatorMetrics) Collect(ch chan<- prometheus.Metric) {
// output cluster operator version and condition info
operators, _ := m.optr.clusterOperatorLister.List(labels.Everything())
for _, op := range operators {
g := m.clusterOperatorUp.WithLabelValues(op.Namespace, op.Name, op.Status.Version)
var firstVersion string
Copy link
Contributor

Choose a reason for hiding this comment

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

are we assuming the operator version is going to be the first?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, I just didn't want to remove the metric value. We're going to need to define it, I'll add a todo

@smarterclayton smarterclayton force-pushed the rename_payload branch 2 times, most recently from 08089e6 to 7444e77 Compare January 23, 2019 17:56
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 23, 2019
One attack vector for clusters is to deny access to new updates or
to deliberately send an older user. This commit ensures the date the
payload was created is reported back through metrics and up via
telemetry. It also adds a new `completed` type for the cluster_version
metric that reports the last successfully applied cluster version and
the date it was successfully applied the first time (from the new
status history field). Finally, we correct the naming for the update
type to match the name of the status field to `desired`.
When we removed the apis this should have been disabled. Leaving the
comment in case we have a need to do this in the future.
Also contains change of CV.Status.Version -> []Version
The contents of an update must be an image ref. We should name the field
what it is.

Depends on openshift/api#175 merging first, then
we can bump and go.
With the change from `Version string` to `Versions []Version` the comparison
is not yet clear. Disable this until the design for version checking lands.
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 23, 2019
@smarterclayton
Copy link
Contributor Author

smarterclayton commented Jan 23, 2019

Fixed up version info, added two, rebased, also fixed a metric panic (previous failure for e2e-aws) where describe wasn't right.

I'm going to look at trying to add a metric integration test in a follow up (but it has to be serial because of global state, which sucks)

@smarterclayton
Copy link
Contributor Author

/retest

@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, smarterclayton

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 [abhinavdahiya,smarterclayton]

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

@smarterclayton
Copy link
Contributor Author

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit d291428 into openshift:master Jan 24, 2019
@openshift-ci-robot
Copy link
Contributor

@smarterclayton: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws 02a389b link /test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 22, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 22, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 23, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 23, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 23, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 23, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 29, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 29, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 30, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Mar 30, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Apr 8, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
wking added a commit to wking/cluster-version-operator that referenced this pull request Aug 6, 2021
Fixing a TODO from 02a389b (sync: Temporarily stop checking version
in ClusterOperator.Status, 2019-01-23, openshift#98).  The semantics of the
'operator' entry have been clear since at least
openshift/api@40c55f8085 (config/v1/types_cluster_operator:
ClusterOperatorStatus doc wordsmithing, 2019-10-28,
openshift/api#501).
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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants