Skip to content
Snippets Groups Projects
  1. Feb 23, 2018
    • Jessica Yuen's avatar
      App spec to take a single destination · 936e31ab
      Jessica Yuen authored
      
      Currently the app.yaml spec takes a list of destinations. The change
      exists to anticipate support for an environment supporting multiple
      clusters or "destinations". The problem is, while the use case makes
      sense for `apply`, and `delete`, it becomes ambiguous which cluster is
      being referred to during commands such as `diff`. We've considered
      specifying a cluster during a `diff`, however, ks currently doesn't have
      a notion of a cluster identity. This change is to update the app.yaml to
      take a single destination to more accurately represent the state of
      things.
      
      Signed-off-by: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      936e31ab
  2. Feb 22, 2018
  3. Feb 21, 2018
  4. Feb 17, 2018
  5. Feb 08, 2018
  6. Feb 05, 2018
  7. Feb 02, 2018
    • Jessica Yuen's avatar
      Migrate environment spec.json to the app.yaml model · 19b3b928
      Jessica Yuen authored
      Currently spec.json contains detail about an environment's namespace and
      server. Following the proposal at
      design/proposals/modular-components.md, this change will consolidate
      environment specifications in the common ksonnet app.yaml file.
      
      An environment specification for the environment "dev", may look as
      follows:
      
      environments:
        dev:
          destinations:
          - namespace: foo
            server: example.com
          k8sVersion: "1.8.1"
          path: dev
          targets:
          - db
      
      Note: This change currently doesn't support
      
      (1) population of the k8sVersion field. This will occur as we migrate
      the environment .metadata folder.
      (2) deployment to more than one destination. This will occur once ks
      supports multi-cluster deployment.
      (3) setting of details other than the env name in `ks env set`. Prior
      to this change, users are able to namespace and server URI, however it
      becomes ambiguous which namespace is being set for an environment where
      there can be multiple destinations. ...
      19b3b928
  8. Feb 01, 2018
  9. Jan 31, 2018
  10. Jan 30, 2018
  11. Jan 26, 2018
  12. Jan 25, 2018
  13. Jan 24, 2018
  14. Jan 22, 2018
  15. Jan 19, 2018