You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am requesting support to deploy OpenShift YAML manifests in Azure DevOps pipelines with this VSTS plugin.
Background:
Azure DevOps pipelines has a number of supported out-of-the-box tasks, of which one of them is "Deploy to Kubernetes". This does a great job with applying Kubernetes manifests with kubectl. This OpenShift plugin has no such feature, and the oc commands that we can perform with the plugin are mostly limited to command line that don't take file inputs. In a GitOps world, this is quite limiting as one would expect that YAML manifests (i.e. a deployment) would be checked into Git and applied as part of the pipeline. The Kubernetes plugin is also not a perfect fit for deploying to OpenShift as it can only manage Kubernetes resources, not OpenShift ones. Thus, I'd like to request the ability to deploy OpenShift YAML manifests as a feature.
The text was updated successfully, but these errors were encountered:
I am requesting support to deploy OpenShift YAML manifests in Azure DevOps pipelines with this VSTS plugin.
Background:
Azure DevOps pipelines has a number of supported out-of-the-box tasks, of which one of them is "Deploy to Kubernetes". This does a great job with applying Kubernetes manifests with kubectl. This OpenShift plugin has no such feature, and the oc commands that we can perform with the plugin are mostly limited to command line that don't take file inputs. In a GitOps world, this is quite limiting as one would expect that YAML manifests (i.e. a deployment) would be checked into Git and applied as part of the pipeline. The Kubernetes plugin is also not a perfect fit for deploying to OpenShift as it can only manage Kubernetes resources, not OpenShift ones. Thus, I'd like to request the ability to deploy OpenShift YAML manifests as a feature.
The text was updated successfully, but these errors were encountered: