Suraj Deshmukh
Suraj Deshmukh
Here the TrafficMetrics CRD yaml file is just a placeholder add configs in this file. https://github.com/deislabs/smi-sdk-go/blob/86042c47396f92f00ad451a030b498bb033277b3/crds/metrics.yaml
The changes made in this PR https://github.com/habitat-sh/habitat-operator/pull/360#issuecomment-421336479 should be reverted to make sure that the operator runs in strict environment by default. This reversion should happen in the same way...
The tests run for the `gh-pages` branch on CircleCI has this warning: > This project is currently running on CircleCI 1.0 which is no longer supported. Please start migrating this...
Two more release after `0.8.0` remove this label. For more context read the **Deprecations** section in this release https://github.com/habitat-sh/habitat-operator/releases/tag/v0.8.0 and https://github.com/habitat-sh/habitat-operator/pull/332
## What's wrong? When a wrong habitat config is provided using kubectl, it is not very clear if something has gone wrong. ## Steps to reproduce Built it from the...
The CRD we auto-generate when the operator is started uses a field in `spec` called `version`, which is marked for deprecation. From API reference [docs](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io) in `1.11`: > version Version...
If no `--kubeconfig` flag is provided default to the kubeconfig in `$HOME/.kube/config`.
RIght now there is no CI that runs with each PR. We should have a setup where each PR triggers a test run. Proposal: We can have a single node...
If I try to stop an already stopped application then traceback is thrown as shown below. It should output it in pretty format (one line ERROR output and exit) ```...
Is it safe/correct behavior to accept empty fields? AtomicApp accetps empty fields: ``` bash $ sudo atomicapp run . -v 1461836612 - [INFO] - cli/main.py - Action/Mode Selected is: run...