CNF-14648: spec updates in the ClusterTemplate #219

edcdavid · 2024-09-26T04:47:53Z

Changes ClusterTemplate spec according to requirements. New format is below:

kind: ClusterTemplate
metadata:
  name: <name of template (name.version)>
  namespace: <namespace of cluster template>
spec:
    name:                          <string, Human readable name of the Template> 
    description:                <string, Human readable description of the Template>
    version:                       <string, Version or generation of the resource as defined by its provider.>
    templateId:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
    characteristics:          <KeyValuePairs, FFS ?>
    metadata:                    <KeyValuePairs, FFS ?>
    templates: (internal to the IMS) 
        hwTemplate:                      <name of hardware template>
        clusterInstanceDefaults: <name of configmap>
        policyTemplateDefaults: <name of configmap>
    templateParameterSchema:
        nodeClusterName:  <string> 
        oCloudSiteId:           <string>
        clusterInstanceParameters:  <schema for clusterInstance data>
        policyTemplateParameters:  <schema for policyTemplate data>

The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>
The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:
the templateID UUID format must be valid
if the TemplateID is empty, one is created automatically during validation.
To use the auto generated TemplateID. Do not configure the templateID field at all in the ClusterTemplate object. If configured and empty, GitOps/ArgoCD will try to reconcile it unsuccessfully.
TODO:
~~unit tests~~
~~operator verification: scorecard, manifest, etc~~
~~system tests~~
~~Debugging Single cluster template commit~~
~~Testing TemplateID auto creation~~
~~unit tests for ExtractSubSchema and InsertSubSchema~~
~~improve schema in unit test~~

openshift-ci-robot · 2024-09-26T04:47:56Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Changes ClusterTemplate spec according to requirements. New format is below:

kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>

The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>
The ClusterTemplate metadata.name must be unique in the cluster

TODO:

~~unit tests~~
system tests
trying new single templateParameterSchema (optional since this is an internal implementation)

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.

openshift-ci · 2024-09-26T04:47:57Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

openshift-ci-robot · 2024-09-26T04:51:39Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Changes ClusterTemplate spec according to requirements. New format is below:

kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>

The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>
The ClusterTemplate metadata.name must be unique in the cluster

TODO:

~~unit tests~~
operator verification: scorecard, manifest, etc
system tests
trying new single templateParameterSchema (optional since this is an internal implementation)

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.

openshift-ci-robot · 2024-09-26T04:53:11Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Work in progress!!!
Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster

TODO:

~~unit tests~~

operator verification: scorecard, manifest, etc

system tests

trying new single templateParameterSchema (optional since this is an internal implementation)

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.

bartwensley · 2024-09-26T13:15:37Z

I think this will need to be updated:

templateParameterSchema:
    nodeClusterName:  <string> 
    oCloudSiteId:           <string>
    clusterInstanceSchema:  <schema for clusterInstance data>
    policyTemplateSchema:  <schema for policyTemplate data>

The clusterInstanceSchema/policyTemplateSchema should be renamed to clusterInstanceParameters/policyTemplateParameters since they are no longer schemas on their own, but just sections in the templateParameterSchema.

irinamihai · 2024-09-26T20:44:37Z

/hold

openshift-ci-robot · 2024-09-26T22:36:08Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Work in progress!!!
Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
TODO:

~~unit tests~~

operator verification: scorecard, manifest, etc

system tests

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.

openshift-ci-robot · 2024-09-26T22:36:29Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Work in progress!!!
Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
TODO:

~~unit tests~~

~~operator verification: scorecard, manifest, etc~~

system tests

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.

openshift-ci-robot · 2024-09-26T22:41:25Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Work in progress!!!
Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
TODO:

~~unit tests~~

~~operator verification: scorecard, manifest, etc~~

~~system tests~~

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.

openshift-ci-robot · 2024-09-27T12:59:50Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceSchema:  <schema for clusterInstance data>
       policyTemplateSchema:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
TODO:

~~unit tests~~

~~operator verification: scorecard, manifest, etc~~

~~system tests~~

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.

edcdavid · 2024-09-27T13:38:46Z

/cc @irinamihai @Missxiaoguo

config/crd/bases/o2ims.oran.openshift.io_clustertemplates.yaml

internal/controllers/clustertemplate_controller.go

bartwensley · 2024-09-30T18:38:31Z

Please update the ClusterTemplate example in the PR description to reflect the updated naming.

openshift-ci-robot · 2024-09-30T21:10:46Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateID:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceParameters:  <schema for clusterInstance data>
       policyTemplateParameters:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
TODO:

~~unit tests~~

~~operator verification: scorecard, manifest, etc~~

~~system tests~~

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.

api/v1alpha1/clustertemplate_types.go

irinamihai · 2024-10-03T17:03:50Z

/unhold

internal/controllers/clustertemplate_controller.go

bundle/manifests/oran-o2ims.clusterserviceversion.yaml

Missxiaoguo · 2024-10-03T19:17:06Z

/lgtm

openshift-ci-robot · 2024-10-03T19:17:59Z

@edcdavid: This pull request references CNF-14648 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.18.0" version, but no target version was set.

In response to this:

Changes ClusterTemplate spec according to requirements. New format is below:
kind: ClusterTemplate
metadata:
 name: <name of template (name.version)>
 namespace: <namespace of cluster template>
spec:
   name:                          <string, Human readable name of the Template> 
   description:                <string, Human readable description of the Template>
   version:                       <string, Version or generation of the resource as defined by its provider.>
   templateId:                 <uuid, Identifier for the O-Cloud Template. This identifier is allocated by the O-Cloud.>  
   characteristics:          <KeyValuePairs, FFS ?>
   metadata:                    <KeyValuePairs, FFS ?>
   templates: (internal to the IMS) 
       hwTemplate:                      <name of hardware template>
       clusterInstanceDefaults: <name of configmap>
       policyTemplateDefaults: <name of configmap>
   templateParameterSchema:
       nodeClusterName:  <string> 
       oCloudSiteId:           <string>
       clusterInstanceParameters:  <schema for clusterInstance data>
       policyTemplateParameters:  <schema for policyTemplate data>
The cluster template validation is updated to include name validation as follows:

The metadata.name must be in the format <spec.name>.<spec.version>

The ClusterTemplate metadata.name must be unique in the cluster
Also includes TemplateID validation:

the templateID UUID format must be valid

if the TemplateID is empty, one is created automatically during validation.
To use the auto generated TemplateID. Do not configure the templateID field at all in the ClusterTemplate object. If configured and empty, GitOps/ArgoCD will try to reconcile it unsuccessfully.
TODO:

~~unit tests~~

~~operator verification: scorecard, manifest, etc~~

~~system tests~~

~~Debugging Single cluster template commit~~

~~Testing TemplateID auto creation~~

~~unit tests for ExtractSubSchema and InsertSubSchema~~

~~improve schema in unit test~~

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.

irinamihai · 2024-10-03T20:35:11Z

/approve

openshift-ci · 2024-10-03T20:35:18Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irinamihai

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~~ [irinamihai]

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

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 26, 2024

edcdavid marked this pull request as ready for review September 26, 2024 04:49

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 26, 2024

openshift-ci bot requested review from danielerez and Jennifer-chen-rh September 26, 2024 04:50

edcdavid added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 26, 2024

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 26, 2024

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 26, 2024

edcdavid force-pushed the update-cluster-template branch from 7553f33 to 6469ebc Compare September 26, 2024 22:34

openshift-ci bot requested review from irinamihai and Missxiaoguo September 27, 2024 13:38

bartwensley reviewed Sep 30, 2024

View reviewed changes

config/crd/bases/o2ims.oran.openshift.io_clustertemplates.yaml Outdated Show resolved Hide resolved

internal/controllers/clustertemplate_controller.go Outdated Show resolved Hide resolved

internal/controllers/clustertemplate_controller.go Outdated Show resolved Hide resolved

edcdavid force-pushed the update-cluster-template branch from 6469ebc to 4ee1a9a Compare September 30, 2024 21:05

edcdavid requested a review from bartwensley September 30, 2024 21:26

Missxiaoguo reviewed Sep 30, 2024

View reviewed changes

api/v1alpha1/clustertemplate_types.go Outdated Show resolved Hide resolved

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 1, 2024

edcdavid force-pushed the update-cluster-template branch from 4ee1a9a to 261959b Compare October 1, 2024 20:05

edcdavid added 4 commits October 3, 2024 12:23

reverting Xvalidation

3c3012b

Addressing comments from irina 2

6618d45

Improve unit test schema - align with Angie's implementation

412e2ef

Addressing comment from Angie

b112bd3

edcdavid force-pushed the update-cluster-template branch from 0512747 to ea85d81 Compare October 3, 2024 16:36

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 3, 2024

Missxiaoguo reviewed Oct 3, 2024

View reviewed changes

internal/controllers/clustertemplate_controller.go Show resolved Hide resolved

edcdavid force-pushed the update-cluster-template branch from ca5ebd1 to e06e164 Compare October 3, 2024 17:47

Merge

0250cde

edcdavid force-pushed the update-cluster-template branch 3 times, most recently from 26f0525 to 7c81b40 Compare October 3, 2024 17:55

edcdavid requested a review from Missxiaoguo October 3, 2024 17:58

edcdavid force-pushed the update-cluster-template branch from 7c81b40 to 8d33e80 Compare October 3, 2024 18:20

bartwensley requested changes Oct 3, 2024

View reviewed changes

bundle/manifests/oran-o2ims.clusterserviceversion.yaml Outdated Show resolved Hide resolved

bundle/manifests/oran-o2ims.clusterserviceversion.yaml Outdated Show resolved Hide resolved

bundle/manifests/oran-o2ims.clusterserviceversion.yaml Outdated Show resolved Hide resolved

openshift-ci bot assigned bartwensley Oct 3, 2024

addressing Angie's comment

d500c6a

edcdavid force-pushed the update-cluster-template branch from 8d33e80 to d500c6a Compare October 3, 2024 18:55

Addressing comments from Bart

039387a

edcdavid requested a review from bartwensley October 3, 2024 19:11

openshift-ci bot assigned Missxiaoguo Oct 3, 2024

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2024

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 3, 2024

openshift-merge-bot bot merged commit 277d987 into openshift-kni:main Oct 3, 2024
8 checks passed

irinamihai mentioned this pull request Oct 4, 2024

CNF-14656: CNF-14653: ClusterRequest to ProvisioningRequest and make it cluster scoped #233

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CNF-14648: spec updates in the ClusterTemplate #219

CNF-14648: spec updates in the ClusterTemplate #219

edcdavid commented Sep 26, 2024 •

edited

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci bot commented Sep 26, 2024

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

bartwensley commented Sep 26, 2024

irinamihai commented Sep 26, 2024

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 27, 2024 •

edited by openshift-ci bot

Loading

edcdavid commented Sep 27, 2024

bartwensley commented Sep 30, 2024

openshift-ci-robot commented Sep 30, 2024 •

edited by openshift-ci bot

Loading

irinamihai commented Oct 3, 2024

Missxiaoguo commented Oct 3, 2024

openshift-ci-robot commented Oct 3, 2024 •

edited by openshift-ci bot

Loading

irinamihai commented Oct 3, 2024

openshift-ci bot commented Oct 3, 2024

CNF-14648: spec updates in the ClusterTemplate #219

CNF-14648: spec updates in the ClusterTemplate #219

Conversation

edcdavid commented Sep 26, 2024 • edited Loading

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

openshift-ci bot commented Sep 26, 2024

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

bartwensley commented Sep 26, 2024

irinamihai commented Sep 26, 2024

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

openshift-ci-robot commented Sep 26, 2024 • edited by openshift-ci bot Loading

openshift-ci-robot commented Sep 27, 2024 • edited by openshift-ci bot Loading

edcdavid commented Sep 27, 2024

bartwensley commented Sep 30, 2024

openshift-ci-robot commented Sep 30, 2024 • edited by openshift-ci bot Loading

irinamihai commented Oct 3, 2024

Missxiaoguo commented Oct 3, 2024

openshift-ci-robot commented Oct 3, 2024 • edited by openshift-ci bot Loading

irinamihai commented Oct 3, 2024

openshift-ci bot commented Oct 3, 2024

edcdavid commented Sep 26, 2024 •

edited

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 26, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 27, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Sep 30, 2024 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Oct 3, 2024 •

edited by openshift-ci bot

Loading