A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/ksonnet/ksonnet/issues/426 below:

Drop-in YAML components with parameters · Issue #426 · ksonnet/ksonnet · GitHub

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT

/kind bug

What happened:

Reported this in #ksonnet slack. but opening a bug so this doesn't get lost. We are very interested in the upcoming drop-in yaml feature coming in 1.10. Our hope is that developers can drop in complete k8s deployment/service YAMLs in the components directory, and parameterize the image name and have this parameter overridden at an environment level. This minimizes the amount of jsonnet/ksonnet knowledge, which is a barrier for adoption for our developers.

When building tip of master to try out the feature, it seems parameters does not work with drop-in yamls. See the following:

$ ls components/
kube-ops-view-deploy.yaml kube-ops-view-svc.yaml    params.libsonnet

$ ks component list
COMPONENT
=========
kube-ops-view-deploy
kube-ops-view-svc

$ ks param set kube-ops-view-deploy image hjacobs/kube-ops-view:0.7.1

$ cat components/params.libsonnet
{
  global: {
  },
  components: {
    "kube-ops-view-deploy-0": {
      image: "hjacobs/kube-ops-view:0.7.1",
    },
  },
}

$ ks param list
COMPONENT INDEX PARAM VALUE
========= ===== ===== =====

What you expected to happen:

There should be something in param list.

Environment:

$ ks version
ksonnet version: dev-2018-04-04T12:43:56-0700
jsonnet version: v0.10.0
client-go version: 1.8-release-1.8

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4