A CLI-supported framework that streamlines writing and deployment of Kubernetes configurations to multiple clusters.
Implemented enhancements:
constructBaseObj out of root.go #72
Fixed bugs:
Closed issues:
ks -v should print an equivalent jsonnet command line string #378
ks param unset command for "unsetting" params #325
ks-generated files #224
ks install #217
expandEnvObjs and expandEnvCmdObjs into one function #70
dep and registry) to pkg kubecfg #65
Merged pull requests:
ks env current command #424 (bryanl)env list #423 (bryanl)show to ksonnet action #415 (bryanl)-- #408 (bryanl)Implemented enhancements:
Fixed bugs:
std.extVar and “\_\_ksonnet/components” when in ksonnet directory #259
Closed issues:
ks param add #211
Merged pull requests:
ks command to work anywhere in app #380 (bryanl)ks commands #362 (bryanl)Fixed bugs:
Closed issues:
Merged pull requests:
e13f7f3 Merge pull request #391 from bryanl/release-0.9.2 3d46bb5 releasing 0.9.2 45553db Merge pull request #389 from bryanl/bug-snippet-jsonnet-10 70cc9dd handle jsonnet ast.ApplyBrace in env files b2f8338 Merge pull request #388 from bryanl/bug-update-env-ns f59c3f1 bug: fix updating env namespace
Automated with GoReleaser Built with go version go1.10 darwin/amd64
e380640 Merge pull request #350 from bryanl/bug-extension-map-container 2b4acaf Merge pull request #349 from bryanl/bug-use-env-params 3b225dd Merge pull request #347 from bryanl/bug-rename-env b70bdab Merge pull request #351 from jessicayuen/changelog-v0.9.1 a901732 Add ChangeLog for v0.9.1 c6aa7d2 bug: mapContainer extension typo e377526 bug: env used incorrent params for rendering e2d51c9 bug: 0.1.0 apps don't rename envs in config e428442 Merge pull request #344 from jessicayuen/param-diff 52af3f6 param diff to print colors 1fdcd06 Fix formatting for param diff aed9283 Merge pull request #343 from jessicayuen/parse-version ad39792 Parse server version from GitVersion
Automated with GoReleaser Built with go version go1.10 darwin/amd64
To update older ksonnet applications, run ks upgrade --help.
This release focuses on two major areas:
Changes to the underlying ksonnet-lib dependency and utilizing them in ks. The changes involve a major uplift to how the ksonnet language APIs are generated, so that support for future Kubernetes versions are easier.
Improvements to the support for environments and components. Environments are now able to specify targets, to apply a subset of components as opposed to all components. We've introduced the concept of component namespaces to add division and hierarchy to components. We've also added commands to support removing and listing of components.
In 0.8.0, each ks application contained a spec.json file per environment. This file contained the environment specification details; corresponding to a Kubernetes cluster server address and namespace.
i.e.,
{
"server": "https://35.230.00.00",
"namespace": "default"
}
With 0.9.0, we will be consolidating majority of the application specification
details into a top-level app.yaml file. As opposed to opening multiple files,
this approach will make it easier for users to configure changes in a single
place. Similar to spec.json, this metadata will be auto-generated when a
environment is created or modified from the command line. However, it is also
meant to be user-modifiable.
i.e.,
apiVersion: 0.0.1
environments:
default:
destination:
namespace: default
server: https://35.230.00.00
k8sVersion: v1.7.0
path: default
kind: ksonnet.io/app
name: new
registries:
incubator:
gitVersion:
commitSha: 422d521c05aa905df949868143b26445f5e4eda5
refSpec: master
protocol: github
uri: github.com/ksonnet/parts/tree/master/incubator
version: 0.0.1
You will notice a couple new fields under the environments field.
destination is identical to the contents of the previous spec.json, containing the server address and namespace that this environment points to.
k8sVersion is the Kubernetes version of the server pointed to at the destination field.
path is the relative path in the environments directory that contains other metadata associated with this environment. By default, path is the environment name.
In 0.8.0, each environment's .metadata directory stored 3 files related to
the generated ksonnet-lib. It was unecessary and also costly as the number of
environments grow. We didn't need to store multiple copies of the same API
version on disk.
With 0.9.0, the Kubernetes API version that each environment uses will be
recorded in the environment specification (as seen in the previous section).
The metadata files are cached once locally per k8s API version in lib.
These files also no longer need to be checked into source control, as ks will auto-generate lib files that aren't found.
In 0.8.0, there was no simple way for users to declare that a environment should only operate on a subset of components.
With 0.9.0, environments can now choose the set of components that they wish to operate (i.e., apply, delete, etc.) on. These targets can be specified in the app.yaml file, mentioned in an earlier section.
For example, if the components directory is structured as follows:
my-ks-app
├── components
│ ├── auth
│ │ ├── ca-secret.jsonnet
│ │ ├── params.libsonnet
│ │ └── tls-certificate.jsonnet
│ ├── dev
│ │ ├── memcached.jsonnet
│ │ └── params.libsonnet
│ ├── params.libsonnet
│ └── prod
│ ...
An environment configuration in app.yaml may appear as follows:
environments:
dev:
k8sVersion: 1.7.0
destinations:
namespace: default
server: https://35.230.00.00
targets:
- auth
- dev
In the above example, the dev environment would only operate on the components within the auth and dev component namespaces.
Note: Component files do not need to be namespaced. Top-level components and individual component files can also be referenced by targets.
ks component list is a new command. See docs here.
ks component rm is a new command. See docs here.
Closed issues:
Merged pull requests:
Automated with GoReleaser Built with go version go1.10 darwin/amd64
Implemented enhancements:
Fixed bugs:
param set incorrectly supporting hyphenated param names #214
Closed issues:
ks version #199
Merged pull requests:
ks registry add #228 (jessicayuen)--name syntax from ks generate commands #205 (abiogenesis-now)Automated with GoReleaser Built with go version go1.9.2 darwin/amd64
This is the initial launch of ksonnet, a CLI-supported framework that streamlines how you write and deploy Kubernetes configurations.
Specifically, ksonnet allows you to:
For more info, see the official website.
kubecfg releases?This release aggregates the work of kubecfg and other ksonnet open-source projects into a single unified tool. If you've been previously involved in the community, these may seem familiar:
ks, the ksonnet command line tool, has built upon the original kubecfg, and added more features for your workflow, with a change in focus to a more declarative, instead of imperative, approach.
The Kubernetes Jsonnet library, ksonnet-lib, provides the core functions for every ksonnet app.
Common Kubernetes configuration patterns are now distributed as prototypes and libraries in a parts repository - previously known as mixins.