Skip to content
This repository has been archived by the owner on Jun 26, 2024. It is now read-only.

User Documentation does not describe the usage of WorkloadResourceMapping #1135

Closed
pedjak opened this issue Apr 27, 2022 · 1 comment · Fixed by #1139
Closed

User Documentation does not describe the usage of WorkloadResourceMapping #1135

pedjak opened this issue Apr 27, 2022 · 1 comment · Fixed by #1139
Labels
kind/bug Something isn't working kind/documentation Improvements or additions to documentation
Milestone

Comments

@pedjak
Copy link
Contributor

pedjak commented Apr 27, 2022

Support for WorkloadResourceMapping was merged in #1086 but the user documentation does not mention it at all. Please keep the doc in sync with the available features, it took us quite some time to bring the doc to the current level, lets continue doing that.

@pedjak pedjak added kind/bug Something isn't working kind/documentation Improvements or additions to documentation labels Apr 27, 2022
@sadlerap
Copy link
Contributor

There are still a few things missing from fully implementing support for ClusterWorkloadResourceMapping resources, namely:

  • Correct rebinding when these resources are modified (semantics regarding this changed rather late in the spec stabilization process)
  • Implementing validation webhooks for these resources
  • Documenting this feature both here in our own documentation and downstream in openshift.

The intention was that #1086 was to implement most of the functionality needed to get support for these resources going, and split off some of the auxiliary things into separate pull requests. I felt that this was a better approach than implementing all of this as one big patch (which is rather difficult to review, can be risky, and would push back this feature even further).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working kind/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants