anchor.diff:  ## Chef Habitat on Kubernetes
   
   Chef Habitat can export your package as a Docker container that runs on Kubernetes in the form of a pod.
  -Additionally, a Chef Habitat bastion pod provides essential gossip ring features like service discovery (binds) and secrets and the required [initial peer](/docs/best-practices/#robust-supervisor-networks)(PID 1) to all other pods.
  +Additionally, a Chef Habitat bastion pod provides essential gossip ring features like service discovery (binds), secrets and the required [initial peer](/docs/best-practices/#robust-supervisor-networks) to all other pods.
   
   Chef Habitat robustly deploys the bastion pod with a Kubernetes stateful set, persistent volume, and liveness checking, which ensures node availability and ring data persistence. The Kubernetes stateful set comes with an attached Kubernetes service that makes discoverable with DNS. Each namespace should contain a single service and stateful set.
   
  
positive.code:       name: hab-bastion
      spec:
        accessModes: [ "ReadWriteOnce" ]
        # uncomment if you don't have a default storageclass
        # storageClassName: "standard"
        resources:
          requests:
            storage: 10Gi
  ```
  
  All of the Habitat supervisor's state data is stored under `/hab/sup` - we mount this on a persistent volume so it gets re-attached if the pod is ever relaunched. The data persists!
  
  ### Create a Kubernetes Deployment that works with the Bastion
  
  
negative.code:         fsGroup: 42
  ```
  
  This section sets the group ownership for the persistent volume mount point so the Habitat Supervisor can write to it.  The Habitat user (`hab`) by default has the uid `42` and the gid `42`.
  
  ```yaml
        containers:
  