How can i export openshift native resource defination to yaml file, like Project/DeploymentConfig/BuildConfig about openshift-apiserver HOT 6 OPEN

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from openshift-apiserver.

/lifecycle frozen

from openshift-apiserver.

There is no CRDs for the internal OpenShift APIServer types. The CR types are provided by the API aggregation step, making the OpenShift-API a required component for providing these endpoints. There are mutations and validations that are performed within the OpenShift API that will also not run if you are able to export the types as CRDs for use with KubeAPI alone. I don't think it's possible to get the same functionality out of the box by exporting the types as CRDs.

from openshift-apiserver.

Or do you just want a type called Project, with no desire for the additional functionality such as ServiceAccount creation and isolation?

from openshift-apiserver.

Or do you just want a type called Project, with no desire for the additional functionality such as ServiceAccount creation and isolation?

yes, i just want type define not implement . I use it for karmada-apiserver which base kube-apiserver for multi-cluster management. karmada-apiserver not support proxy openshift only types

from openshift-apiserver.

Hi MichaelWasher,

I have same question like how do we export native CRDs like deploymentConfig..etc. My use case is "we are using CDK8s for our manifest generating and it is very easy to import existing CRD into libraries but didn't find a way to get this openshift native API CRDs "deploymentconfig/route/..etc".

from openshift-apiserver.