Skip to content

CheCluster's cleaned up fields are not getting reflected on DevWorkspaceOperatorConfig #23502

@rohanKanojia

Description

@rohanKanojia

Describe the bug

Originally posted by @dkwon17 in eclipse-che/che-operator#2004 (comment)

It seems that when we clean up some fields from CheCluster CustomResource, they are not getting reflected in managed DevWorkspaceOperatorConfig instance properly.

This was observed during review of eclipse-che/che-operator#2004 but it seemed general issue affecting other fields too (see eclipse-che/che-operator#2004 (comment)).

Che version

7.106@latest

Steps to reproduce

  1. Install che-operator
  2. In CheCluster configuration, set:
    storage:
      perUserStrategyPvcConfig:
        storageAccessMode:
          - ReadWriteMany
      pvcStrategy: per-user
  1. Then remove perUserStrategyPvcConfig:
  storage:
    pvcStrategy: per-user
  1. Check DWOC, it still has ReadWriteMany:
apiVersion: controller.devfile.io/v1alpha1
config:
  workspace:
    storageAccessMode:
      - ReadWriteMany

Expected behavior

Whenever CheCluster configuration fields are cleaned up, they should be reflected in managed DevWorkspaceOperatorConfig CustomResource as well.

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/latest

Environment

Linux

Eclipse Che Logs

Additional context

No response

Metadata

Metadata

Assignees

Labels

area/che-operatorIssues and PRs related to Eclipse Che Kubernetes Operatorkind/bugOutline of a bug - must adhere to the bug report template.severity/P2Has a minor but important impact to the usage or development of the system.team/BThis team is responsible for the Web Terminal, the DevWorkspace Operator.

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions