1. 05 Mar, 2018 2 commits
  2. 01 Mar, 2018 3 commits
  3. 28 Feb, 2018 3 commits
  4. 27 Feb, 2018 3 commits
  5. 26 Feb, 2018 5 commits
  6. 25 Feb, 2018 1 commit
  7. 23 Feb, 2018 4 commits
  8. 22 Feb, 2018 3 commits
  9. 21 Feb, 2018 2 commits
  10. 17 Feb, 2018 3 commits
  11. 08 Feb, 2018 4 commits
  12. 05 Feb, 2018 1 commit
  13. 02 Feb, 2018 1 commit
    • 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. We will encourage configuration in
      app.yaml itself.
      (4) targets. This will come in a later change.
      Signed-off-by: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      19b3b928
  14. 01 Feb, 2018 5 commits