kameshsampath

#!/bin/bash

set -e 
# Create a profile called "servicemesh"
minishift profile set servicemesh 
# give the profile 8GB of memory
minishift config set memory 8GB 
# give the profile 4 CPU
minishift config set cpus 4
# adding container image caching to allow faster profile setup 

kameshsampath

#!/bin/bash

set -e 
git clone https://github.com/minishift/minishift-addons
minishift addon install ./minishift-addons/add-ons/istio

kameshsampath

#!/bin/bash 

set -e 

minishift addon enable istio
minishift addon apply istio 

kameshsampath

cd $PROJECT_HOME/service
kubectl create namespace demos
kubectl label namespace demos istio-injection=enabled
eval $(minikube docker-env)
docker build -t dev.local/rhdevelopers/node-greeter:0.0.1 .
kubectl apply -f service.yaml -n demos

kameshsampath

INGRESSGATEWAY=istio-ingressgateway
IP_ADDRESS="$(minishift ip):$(kubectl get svc $INGRESSGATEWAY --namespace istio-system --output 'jsonpath={.spec.ports[?(@.port==80)].nodePort}')"

curl -H "Host: greeter.demos.example.com" $IP_ADDRESS

kameshsampath

Instead of creating a new gist, you can update an existing one by passing its ID
or URL with "-u". For this to work, you must be logged in, and have created the
original gist with the same GitHub account.

kameshsampath

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: customer
    version: v1
  name: customer
spec:
  replicas: 1
  selector:

kameshsampath

apiVersion: 1.0.0
metadata:
  name: quarkus-workshop
projects:
  - name: quarkus-tutorial
    source:
      type: git
      location: 'https://github.com/redhat-developer-demos/quarkus-tutorial.git'
components:
  - id: redhat/vscode-yaml/latest

kameshsampath

apiVersion: operators.coreos.com/v1
kind: CatalogSourceConfig
metadata:
  name: rhd-workshop-packages
  namespace: openshift-marketplace
spec:
  targetNamespace: openshift-operators
  packages: knative-serving-operator,knative-eventing-operator,openshift-pipelines-operator,elasticsearch-operator,jaeger-product,kiali-ossm,servicemeshoperator
  source: community-operators

kameshsampath

2019/12/20 02:15:28 Camel K is correctly installed in the cluster.
2019/12/20 02:15:29 Registering Components.
2019/12/20 02:15:29 Setting up Controllers.
2019/12/20 02:15:29 Adding the Camel Source controller.
{"level":"panic","ts":1576808129.4429235,"logger":"fallback","caller":"addressable/addressable.go:56","msg":"Unable to fetch knative.dev/pkg/apis/duck.InformerFactory from context.","stacktrace":"knative.dev/eventing-contrib/vendor/knative.dev/pkg/client/injection/ducks/duck/v1/addressable.Get\n\t/home/prow/go/src/knative.dev/eventing-contrib/vendor/knative.dev/pkg/client/injection/ducks/duck/v1/addressable/addressable.go:56\nknative.dev/eventing-contrib/vendor/knative.dev/pkg/resolver.NewURIResolver\n\t/home/prow/go/src/knative.dev/eventing-contrib/vendor/knative.dev/pkg/resolver/addressable_resolver.go:53\nknative.dev/eventing-contrib/camel/source/pkg/reconciler.Add\n\t/home/prow/go/src/knative.dev/eventing-contrib/camel/source/pkg/reconciler/camelsource.go:80\nmain.main\n\t/home/prow/go/src/knative.