Openshift objects validation

[zegl]

Openshift objects validation

[zegl]

Hey, I’m not very familiar with OpenShift, but I don’t see any reason for why this project should not support it. Pull Requests are welcome.

[030]

@andywow Could you indicate what Kind of OpenShift objects should be validated, e.g. BuildConfigs, DeploymentConfigs, ImageStreams, Routes. I think that we should to validate one.

[030]

@zegl could you give me some pointers? For example, an OpenShift DeploymentConfig is the equivalent of a Deployment in k8s. Should I create a new file? What is the best way to start in this project?

apiVersion: v1
kind: DeploymentConfig
metadata:
  name: frontend
spec:
  replicas: 5
  selector:
    name: frontend
  template: { ... }
  triggers:
  - type: ConfigChange 
  - imageChangeParams:
      automatic: true
      containerNames:
      - helloworld
      from:
        kind: ImageStreamTag
        name: hello-openshift:latest
    type: ImageChange  
  strategy:
    type: Rolling      

Source: https://docs.openshift.com/container-platform/4.1/applications/deployments/what-deployments-are.html

[neilchaudhuri]

Curious if anyone has figured out a way to do this as an extension of the current library or if it will take a PR to make it happen