Re: OpenShift plans

[Dan Callaghan]

Excerpts from Dan Callaghan's message of 2017-07-06 09:05 +10:00:
>  Here is an example below (and btw I suggest YAML over JSON because 
>  it's easier to edit, oc happily deals in either format). You can see 
>  large parts are not configuration, for example the top-level "status" 
>  key, "creationTimestamp", the JSON blob in 
>  "kubectl.kubernetes.io/last-applied-configuration" annotation, 
>  "selfLink", "uid", etc. 
Oh I just remembered... The oc get command *does* have an option 
--export which is supposed to strip out all this stuff. But it seems to 
leave some things in. For example the selfLink, status, 
last-applied-configuration are all still present (although there is 
certainly *less* gunk):

$ oc -n waiverdb-stg get route waiverdb-stg-web -o yaml --export
apiVersion: v1
kind: Route
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration:
'{"kind":"Route","apiVersion":"v1","metadata":{"name":"waiverdb-stg-web","creationTimestamp":null,"labels":{"app":"waiverdb"}},"spec":{"host":"waiverdb.stage.engineering.redhat.com","to":{"kind":"Service","name":"waiverdb-stg-web","weight":null},"port":{"targetPort":"web"},"tls":{"termination":"edge","insecureEdgeTerminationPolicy":"Redirect"}},"status":{"ingress":null}}'
  creationTimestamp: null
  labels:
    app: waiverdb
  name: waiverdb-stg-web
  selfLink: /oapi/v1/namespaces//routes/waiverdb-stg-web
spec:
  host: waiverdb.stage.engineering.redhat.com
  port:
    targetPort: web
  tls:
    insecureEdgeTerminationPolicy: Redirect
    termination: edge
  to:
    kind: Service
    name: waiverdb-stg-web
    weight: 100
  wildcardPolicy: None
status:
  ingress: null

-- 
Dan Callaghan <dcallagh(a)redhat.com&gt;
Senior Software Engineer, Products & Technologies Operations
Red Hat