kabanero-io / kabanero-foundation Goto Github PK
View Code? Open in Web Editor NEWThis repo will be archived soon.
This repo will be archived soon.
A script to collection relevant debug information
Execute the script kabanero-mustgather.sh
while logged in as a cluster-admin to gather information about the state of the kabanero foundation components, which includes appsody, istio, kabanero, knative, and tekton. The script collections get
and describe
information about these components, as well the pod logs
.
It is important to have uninstall script for kabanero to clean all the resources it installed and created. So that fresh re-install kabanero on the same cluster will work.
At present, the pipeline is an instance
of tekton pipelines customized for kabanero projects. Few pain points with this approach:
kubectl / oc
tasks as pre-reqsyaml-complexities
and k8s-internals
The proposal is to integrate
pipeline as a first-class citizen into kabanero capability by providing a high level abstraction on its ingredients: more specifically, the tasks and resources. The objective is to expose an interface through which a user can define their own pipeline with the help of interactive with an intuitive workflow model.
Proposal 1:
Define a custom grammer, specification and a template for defining pipelines that the user can customize. It still sues YAML syntax, but the verbs and qualifiers are made more simpler, and high level.
Expose a command line interface that will compile the high level pipeline description manifest, and generate a fully-blown working set of pipelines that can be applied to k8s clusters.
Proposal 2:
Expose a command line interface that interacts with the user and constructs a pipeline from scratch, through a series of questions. Much more flexible than first one, but much more complex to implement.
these can be a fit for upstream tekton/pipeline project as well, but the advantage of kabanero are:
LMK WDYT!
Using the latest kabanero install, seeing issue creating a webhook from Tekton dashboard.
Thanks @dacleyra for looking into it.
Kabanero yaml document should be colocated with install-kabanero-foundation.sh
or the location of the customized Kabanero yaml document should be able to be passed in as a parameter to install-kabanero-foundation.sh, otherwise when Todd customizes:
https://github.com/kabanero-io/kabanero-operator/blob/master/config/samples/full.yaml
How will it know where the customized copy is?
Currently, during application development with appsody (init) certain version of collection repository is used. For example:
https://github.com/kabanero-io/collections/releases/download/v0.1.2/kabanero-index.yaml
But these versions change for new release. How would kabanero pipelines handle applications built with multiple collection versions? It would probably be a Todd/Champ decision to decide which versions to support though. I have seen pipeline tasks failing when the application is created with old collections.
Unable to complete build for sample hello world app (https://github.com/dacleyra/appsody-hello-world), failed with following error.
Downloading from central: https://repo.maven.apache.org/maven2/io/openliberty/openliberty-runtime/19.0.0.8/openliberty-runtime-19.0.0.8.zip
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:12 min
[INFO] Finished at: 2019-09-04T16:26:13Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.wasdev.wlp.maven.plugins:liberty-maven-plugin:2.6.4:install-server (create-server) on project starter-app: Unable to resolve artifact: io.openliberty:openliberty-runtime:19.0.0.8: Could not transfer artifact io.openliberty:openliberty-runtime:zip:19.0.0.8 from/to localrepository (/mvn/repository): Cannot access /mvn/repository with type default using the available connector factories: BasicRepositoryConnectorFactory: Cannot access /mvn/repository using the registered transporter factories: WagonTransporterFactory: Unsupported transport protocol -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
error building image: error building stage: waiting for process to exit: exit status 1
Failed to pull image "registry.access.redhat.com/ubi8/ubi:latest": rpc error: code = Unknown desc = open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory
oc describe pod manual-pipeline-run-r-24410-deploy-task-xt2sk-pod-4835bb
Name: manual-pipeline-run-r-24410-deploy-task-xt2sk-pod-4835bb
Namespace: kabanero
Priority: 0
PriorityClassName: <none>
Node: okd.XXX.XXX.XXX.XXX.nip.io/XXX.XXX.XXX.XXX
Start Time: Fri, 06 Sep 2019 15:42:56 +0800
Labels: rebuilds=manual-pipeline-run-r-24410
tekton.dev/pipeline=java-microprofile-build-deploy-pipeline
tekton.dev/pipelineRun=manual-pipeline-run-r-24410
tekton.dev/pipelineTask=deploy-task
tekton.dev/task=java-microprofile-deploy-task
tekton.dev/taskRun=manual-pipeline-run-r-24410-deploy-task-xt2sk
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"tekton.dev/v1alpha1","kind":"PipelineRun","metadata":{"annotations":{},"name":"manual-pipeline-run","namespace":"kabanero"}...
manifestival: new
openshift.io/scc: anyuid
tekton.dev/ready:
Status: Pending
IP: 10.129.0.103
Controlled By: TaskRun/manual-pipeline-run-r-24410-deploy-task-xt2sk
Init Containers:
step-credential-initializer-6ql6f:
Container ID: docker://b2eca03b9c34bd574b4183309b5d4711ec813914ea8584639fb32bfc7b1d2242
Image: quay.io/openshift-pipeline/tektoncd-pipeline-creds-init:v0.5.2
Image ID: docker-pullable://quay.io/openshift-pipeline/tektoncd-pipeline-creds-init@sha256:e0b94791baea49f8c9e087d3fa98c7310d09dd805d74261b0056420a2686fb95
Port: <none>
Host Port: <none>
Command:
/ko-app/creds-init
Args:
-docker-cfg=appsody-sa-dockercfg-m9vvt
State: Terminated
Reason: Completed
Exit Code: 0
Started: Fri, 06 Sep 2019 15:42:59 +0800
Finished: Fri, 06 Sep 2019 15:42:59 +0800
Ready: True
Restart Count: 0
Environment:
HOME: /builder/home
Mounts:
/builder/home from home (rw)
/var/build-secrets/appsody-sa-dockercfg-m9vvt from secret-volume-appsody-sa-dockercfg-m9vvt-srlzd (rw)
/var/run/secrets/kubernetes.io/serviceaccount from appsody-sa-token-x8dwg (ro)
/workspace from workspace (rw)
step-place-tools:
Container ID: docker://fadd05c44f5f5b7cdd4c966e9d1e4d5b3de5f2fec4a3ce346b1dc38b2953eb34
Image: quay.io/openshift-pipeline/tektoncd-pipeline-entrypoint:v0.5.2
Image ID: docker-pullable://quay.io/openshift-pipeline/tektoncd-pipeline-entrypoint@sha256:9199472c029ac43c44c069db41ea525c94ef63f5c2737410709f2e33c511a7d4
Port: <none>
Host Port: <none>
Command:
/bin/sh
Args:
-c
cp /ko-app/entrypoint /builder/tools/entrypoint
State: Terminated
Reason: Completed
Exit Code: 0
Started: Fri, 06 Sep 2019 15:43:00 +0800
Finished: Fri, 06 Sep 2019 15:43:00 +0800
Ready: True
Restart Count: 0
Environment:
HOME: /builder/home
Mounts:
/builder/home from home (rw)
/builder/tools from tools (rw)
/var/run/secrets/kubernetes.io/serviceaccount from appsody-sa-token-x8dwg (ro)
/workspace from workspace (rw)
Containers:
step-git-source-git-source-cvkg6:
Container ID: docker://9f4e736148082f1ad95a2a4fc0a4b92d892cb30c6280ad3026f43dd05b476967
Image: quay.io/openshift-pipeline/tektoncd-pipeline-git-init:v0.5.2
Image ID: docker-pullable://quay.io/openshift-pipeline/tektoncd-pipeline-git-init@sha256:b49fd131d93cd525a2b5898e962c74b7e57f63be6d1bce8c5617a678628f2aee
Port: <none>
Host Port: <none>
Command:
/builder/tools/entrypoint
Args:
-wait_file
/builder/downward/ready
-post_file
/builder/tools/0
-wait_file_content
-entrypoint
/ko-app/git-init
--
-url
https://github.com/dacleyra/appsody-hello-world/
-revision
master
-path
/workspace/git-source
State: Running
Started: Fri, 06 Sep 2019 15:43:01 +0800
Ready: True
Restart Count: 0
Requests:
cpu: 0
ephemeral-storage: 0
memory: 0
Environment:
HOME: /builder/home
Mounts:
/builder/downward from downward (rw)
/builder/home from home (rw)
/builder/tools from tools (rw)
/var/run/secrets/kubernetes.io/serviceaccount from appsody-sa-token-x8dwg (ro)
/workspace from workspace (rw)
step-modify-app-deploy-yaml-step:
Container ID:
Image: registry.access.redhat.com/ubi8/ubi:latest
Image ID:
Port: <none>
Host Port: <none>
Command:
/builder/tools/entrypoint
Args:
-wait_file
/builder/tools/0
-post_file
/builder/tools/1
-entrypoint
/bin/bash
--
-cex
echo "Checking for app-deploy.yaml"
APP_DEPLOY_YAML=$(find /workspace/git-source -name ${YAMLFILE} -type f)
if [ -z "$APP_DEPLOY_YAML" ]; then
echo "ERROR: app-deploy.yaml not found in project. Please run appsody deploy --generate-only in your appsody project to generate the app-deploy.yaml and check it into your repo before running the pipeline."
exit 1
fi
# Replace the image name
echo "Replacing image name in app-deploy.yaml ${IMG}"
sed -i -e 's#applicationImage: .*$#applicationImage: '"$IMG"'#g' ${APP_DEPLOY_YAML}
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Requests:
cpu: 0
ephemeral-storage: 0
memory: 0
Environment:
HOME: /builder/home
REPO: java-microprofile
IMG: docker-registry.default.svc:5000/kabanero/java-microprofile
YAMLFILE: app-deploy.yaml
Mounts:
/builder/home from home (rw)
/builder/tools from tools (rw)
/var/run/secrets/kubernetes.io/serviceaccount from appsody-sa-token-x8dwg (ro)
/workspace from workspace (rw)
step-deploy-image-step:
Container ID: docker://cfac61d385537d253d04c872f97a55074c7dbd1427373e0d690e88e4ff02ac05
Image: lachlanevenson/k8s-kubectl
Image ID: docker-pullable://docker.io/lachlanevenson/k8s-kubectl@sha256:c794866697bee0787ef2957a27d593146e9d78a3aa55aea66eb18efa07d4aeeb
Port: <none>
Host Port: <none>
Command:
/builder/tools/entrypoint
Args:
-wait_file
/builder/tools/1
-post_file
/builder/tools/2
-entrypoint
/bin/sh
--
-c
find /workspace/git-source -name ${YAMLFILE} -type f|xargs kubectl apply -f
State: Running
Started: Fri, 06 Sep 2019 15:43:07 +0800
Ready: True
Restart Count: 0
Requests:
cpu: 0
ephemeral-storage: 0
memory: 0
Environment:
HOME: /builder/home
YAMLFILE: app-deploy.yaml
Mounts:
/builder/home from home (rw)
/builder/tools from tools (rw)
/var/run/secrets/kubernetes.io/serviceaccount from appsody-sa-token-x8dwg (ro)
/workspace from workspace (rw)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
tools:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
downward:
Type: DownwardAPI (a volume populated by information about the pod)
Items:
metadata.annotations['tekton.dev/ready'] -> ready
workspace:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
home:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
secret-volume-appsody-sa-dockercfg-m9vvt-srlzd:
Type: Secret (a volume populated by a Secret)
SecretName: appsody-sa-dockercfg-m9vvt
Optional: false
appsody-sa-token-x8dwg:
Type: Secret (a volume populated by a Secret)
SecretName: appsody-sa-token-x8dwg
Optional: false
QoS Class: BestEffort
Node-Selectors: node-role.kubernetes.io/compute=true
Tolerations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 30m default-scheduler Successfully assigned kabanero/manual-pipeline-run-r-24410-deploy-task-xt2sk-pod-4835bb to okd.XXX.XXX.XXX.XXX.nip.io
Normal Pulled 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Container image "quay.io/openshift-pipeline/tektoncd-pipeline-creds-init:v0.5.2" already present on machine
Normal Created 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Created container
Normal Started 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Started container
Normal Started 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Started container
Normal Pulled 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Container image "quay.io/openshift-pipeline/tektoncd-pipeline-entrypoint:v0.5.2" already present on machine
Normal Created 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Created container
Normal Pulling 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io pulling image "lachlanevenson/k8s-kubectl"
Normal Pulled 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Container image "quay.io/openshift-pipeline/tektoncd-pipeline-git-init:v0.5.2" already present on machine
Normal Created 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Created container
Normal Started 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Started container
Normal Pulled 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Successfully pulled image "lachlanevenson/k8s-kubectl"
Normal Created 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Created container
Normal Started 30m kubelet, okd.XXX.XXX.XXX.XXX.nip.io Started container
Warning Failed 29m (x2 over 30m) kubelet, okd.XXX.XXX.XXX.XXX.nip.io Failed to pull image "registry.access.redhat.com/ubi8/ubi:latest": rpc error: code = Unknown desc = open /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt: no such file or directory
Warning Failed 29m (x2 over 30m) kubelet, okd.XXX.XXX.XXX.XXX.nip.io Error: ErrImagePull
Normal Pulling 29m (x2 over 30m) kubelet, okd.XXX.XXX.XXX.XXX.nip.io pulling image "registry.access.redhat.com/ubi8/ubi:latest"
Warning Failed 4m59s (x110 over 30m) kubelet, okd.XXX.XXX.XXX.XXX.nip.io Error: ImagePullBackOff
Normal BackOff 11s (x131 over 30m) kubelet, okd.XXX.XXX.XXX.XXX.nip.io Back-off pulling image "registry.access.redhat.com/ubi8/ubi:latest"
I have kabanero installed using the scripts. When I login to OKD console, I see the following error after kabanero namespace is selected.
When you click on the Open Metric URL
, It takes to a webpage https://hawkular-metrics./hawkular/metrics
@davco01a commented on Thu Aug 01 2019
Enhance the script to do the following after the initial istio and kabanero pod setup:
apiVersion: v1
kind: Secret
metadata:
name: my-docker-secret
annotations:
tekton.dev/docker-0: https://index.docker.io/v1/
type: kubernetes.io/basic-auth
stringData:
username: <your docker userid>
password: <your docker password>
kubectl apply -f my-docker-secret.yaml
secrets:
- name: my-docker-secret
params:
- name: url
value: index.docker.io/your-userid/my-appsody-image
type: image
spec:
params:
- name: revision
value: master
- name: url
value: https://github.com/your-userid/appsody-test-project
kubectl apply -f appsody-pipeline-resources.yaml
@bschrammIBM commented on Thu Aug 22 2019
This should be assigned to engineer, although the script is located in the /docs directory. https://github.com/kabanero-io/docs/tree/master/ref/scripts/install-kabanero-foundation.sh.
@davco01a commented on Tue Sep 03 2019
John Duimovich:fishing_pole_and_fish: 4 days ago
@dacohen There are a bunch of scripts in https://github.ibm.com/John-Duimovich/kabanero-demo.git which do the automated creation of an appsody app, create IBM git repos, add secrets that may help you here. See appsody-ibm-script as the start it calls a whack of utils utils for each step. I also have a simpler 'tekton only" demo which is derived from these but also ported to install on local windows docker. There is a run-webhook script which can run a pipeline for your app --- if we can hooked it to kabanero collections so you know which one to run, it would be pretty sweet.
The Readme should include information on what makes up the foundation, what role the kabanero operator plays, how the eventing infrastructure plays.
Provide a common install script that used common between Kabanero and products that imbed it.
Optionally install Eclipse Che as a hosted IDE.
Optionally install KUI
Using the script in the PR attached to #40 I tried to delete "everything" .
The first runs using -r and -d deleted alot, but it ends up hanging and in the end routes.serving.knative.dev is still there:
./kab-uninstall.sh -r
---------- Deleting 'all' in istio-system ----------
No resources found
---------- Deleting 'all' in istio-operator ----------
No resources found
---------- Deleting 'all' in kabanero ----------
route.serving.knative.dev "appsody-hello-world" deleted
route.serving.knative.dev "webhooks-extension-sink" deleted
^C
2019-08-31 06:07:35 ⌚ tsees-mbp in ~/github.com/kabanero-foundation/scripts
± |uninstall → origin ✓| → ./kab-uninstall.sh -d
Error from server (NotFound): apiservices.apiregistration.k8s.io "v1beta1.custom.metrics.k8s.io" not found
---------- Deleteing dangling resources for istio-system ----------
---------- Deleteing dangling resources for istio-operator ----------
---------- Deleteing dangling resources for kabanero ----------
route.serving.knative.dev "appsody-hello-world" deleted
^C
2019-08-31 06:50:33 ⌚ tsees-mbp in ~/github.com/kabanero-foundation/scripts
oc get all
NAME URL READY REASON
route.serving.knative.dev/appsody-hello-world http://appsody-hello-world.kabanero.my.openshift.master.default.subdomain True
route.serving.knative.dev/webhooks-extension-sink http://webhooks-extension-sink.kabanero.my.openshift.master.default.subdomain True
oc get crds --all-namespaces | grep knative
routes.serving.knative.dev 2019-08-02T18:35:52Z
Looks like istio and tekton aren't fully uninstalled either:
oc get crds --all-namespaces
NAME CREATED AT
adapters.config.istio.io 2019-08-02T18:33:31Z
alertmanagers.monitoring.coreos.com 2019-07-30T18:01:52Z
apikeys.config.istio.io 2019-08-02T18:33:30Z
attributemanifests.config.istio.io 2019-08-02T18:33:30Z
authorizations.config.istio.io 2019-08-02T18:33:30Z
bundlebindings.automationbroker.io 2019-07-30T18:08:42Z
bundleinstances.automationbroker.io 2019-07-30T18:08:50Z
bundles.automationbroker.io 2019-07-30T18:08:46Z
bypasses.config.istio.io 2019-08-02T18:33:30Z
checknothings.config.istio.io 2019-08-02T18:33:30Z
circonuses.config.istio.io 2019-08-02T18:33:30Z
clustertasks.tekton.dev 2019-08-02T18:35:42Z
deniers.config.istio.io 2019-08-02T18:33:30Z
destinationrules.networking.istio.io 2019-08-02T18:33:30Z
edges.config.istio.io 2019-08-02T18:33:31Z
envoyfilters.networking.istio.io 2019-08-02T18:33:30Z
extensions.dashboard.tekton.dev 2019-08-02T18:35:55Z
fluentds.config.istio.io 2019-08-02T18:33:30Z
gateways.networking.istio.io 2019-08-02T18:33:30Z
handlers.config.istio.io 2019-08-02T18:33:31Z
httpapispecbindings.config.istio.io 2019-08-02T18:33:30Z
httpapispecs.config.istio.io 2019-08-02T18:33:30Z
installs.tekton.dev 2019-08-02T18:33:37Z
instances.config.istio.io 2019-08-02T18:33:31Z
kubernetesenvs.config.istio.io 2019-08-02T18:33:30Z
kuberneteses.config.istio.io 2019-08-02T18:33:30Z
listcheckers.config.istio.io 2019-08-02T18:33:30Z
listentries.config.istio.io 2019-08-02T18:33:30Z
logentries.config.istio.io 2019-08-02T18:33:30Z
memquotas.config.istio.io 2019-08-02T18:33:30Z
meshpolicies.authentication.istio.io 2019-08-02T18:33:30Z
metrics.config.istio.io 2019-08-02T18:33:31Z
noops.config.istio.io 2019-08-02T18:33:30Z
opas.config.istio.io 2019-08-02T18:33:30Z
pipelineresources.tekton.dev 2019-08-02T18:35:43Z
pipelineruns.tekton.dev 2019-08-02T18:35:43Z
pipelines.tekton.dev 2019-08-02T18:35:42Z
policies.authentication.istio.io 2019-08-02T18:33:30Z
prometheuses.config.istio.io 2019-08-02T18:33:30Z
prometheuses.monitoring.coreos.com 2019-07-30T18:01:52Z
prometheusrules.monitoring.coreos.com 2019-07-30T18:01:52Z
quotas.config.istio.io 2019-08-02T18:33:31Z
quotaspecbindings.config.istio.io 2019-08-02T18:33:30Z
quotaspecs.config.istio.io 2019-08-02T18:33:30Z
rbacconfigs.rbac.istio.io 2019-08-02T18:33:31Z
rbacs.config.istio.io 2019-08-02T18:33:30Z
redisquotas.config.istio.io 2019-08-02T18:33:30Z
reportnothings.config.istio.io 2019-08-02T18:33:31Z
routes.serving.knative.dev 2019-08-02T18:35:52Z
rules.config.istio.io 2019-08-02T18:33:30Z
servicecontrolreports.config.istio.io 2019-08-02T18:33:31Z
servicecontrols.config.istio.io 2019-08-02T18:33:30Z
serviceentries.networking.istio.io 2019-08-02T18:33:30Z
servicemonitors.monitoring.coreos.com 2019-07-30T18:01:52Z
servicerolebindings.rbac.istio.io 2019-08-02T18:33:31Z
serviceroles.rbac.istio.io 2019-08-02T18:33:31Z
signalfxs.config.istio.io 2019-08-02T18:33:30Z
solarwindses.config.istio.io 2019-08-02T18:33:30Z
stackdrivers.config.istio.io 2019-08-02T18:33:30Z
statsds.config.istio.io 2019-08-02T18:33:30Z
stdios.config.istio.io 2019-08-02T18:33:30Z
taskruns.tekton.dev 2019-08-02T18:35:44Z
tasks.tekton.dev 2019-08-02T18:35:44Z
templates.config.istio.io 2019-08-02T18:33:31Z
tracespans.config.istio.io 2019-08-02T18:33:31Z
virtualservices.networking.istio.io 2019-08-02T18:33:30Z
oc get projects
NAME DISPLAY NAME STATUS
default Active
kabanero Terminating
kube-public Active
kube-service-catalog Active
kube-system Active
management-infra Active
openshift Active
openshift-ansible-service-broker Active
openshift-console Active
openshift-infra Active
openshift-logging Active
openshift-monitoring Active
openshift-node Active
openshift-sdn Active
openshift-template-service-broker Active
openshift-web-console Active
kabanero has been in Terminating state for several days (since i first tried to delete all)
"installation scripts from our documentation repository" link is broke
https://github.com/kabanero-io/kabanero-foundation/blob/master/scripts/README.md
Differentiate what will be provided by the customer before we install and what we will install.
Please update https://github.com/kabanero-io/kabanero-foundation/tree/master/scripts/README.md to remind users to change the my.openshift.master.default.subdomain
to their actual subdomain's name when running the following command:
openshift_master_default_subdomain=my.openshift.master.default.subdomain ./install-kabanero-foundation.sh
Swift is not being supported, that information creates confusion.
On this page, in the Installation
section:
https://kabanero.io/docs/ref/general/installing-kabanero-foundation.html
I don't see any mention of copying and modifying:
https://github.com/kabanero-io/kabanero-operator/blob/master/config/samples/full.yaml
prior to running the install-kabanero-foundation.sh script
The initial drop of the install script installs Istio using the pattern based on Knative. That level of Istio is 1.0.7 and does not match the level that is preferred for the Tekton Dashboard 0.1.1.
Knative has removed this same Istio install from their distribution, and we need to find an alternate "demo" distribution.
The install script should check to see if Istio is already installed and if it is, skip Istio setup.
@dianak2016 commented on Mon Sep 23 2019
Kabanero would like to offer Che as a first-class deployment, managed by the Kabanero operator. The Kabanero operator today can install Che, and the consumer can configure Che workspaces as desired. From a Kabanero strategic point of view, it is important that the Che support includes an Appsody development experience -- at the moment, it is understood by the Kabanero team that while Che can effectively provide the Codewind experience in a hosted Kubernetes environment, the Appsody extension is not currently supported in this environment.
This makes the usage of Kabanero collections impossible in the Kabanero managed Che.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.