Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
Local installation requires the Hyperkit driver for Minikube, which is only supported on macOS.

OS: Ubuntu 16.04
Minikube version: 0.28.0

Expected result

I expect the local installation script to work with at least one Minikube driver supported on Linux.

Actual result

$ cmd/run.sh 

################################################################################
# Minikube setup with driver hyperkit
################################################################################

Parsing DEX TLS certificate secret...
Saving DEX TLS certificate in the container file: /home/username/.minikube/files/dex-ca.crt...
DEX TLS certificate saved in the container: /home/username/.minikube/files/dex-ca.crt
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
F0726 10:27:51.645246   28633 cluster.go:212] Unsupported driver: hyperkit

Steps to reproduce

Run local installation script on Linux.

Confirm these statements before you submit the issue:

• [ X] I have searched open and closed issues for duplicates.
• [X ] I have read the contributing guidelines.

Description
Hi Colleagues,
The API Gateway Architecture Documentation (kyma/docs/api-gateway/docs/005-architecture.md) still references Istio Igress which should be changed to Virtual Service.

Cheers

Andreas

Expected result

N/A

Actual result

N/A

Steps to reproduce

N/A

Troubleshooting

N/A

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

In local installation guide describe "trusting" the Kyma certificate for platforms other than MacOS.
What was already provided by community:

 Linux

If you're using Linux, you can also follow this official wiki pages:

Configuring SSL certificates on Linux.
NSS Shared DB And LINUX
NSS Shared DB Howto

Basically:

click the lock icon with an X,
choose Certificate Information
go to Details tab
Click on Export... (save as a file)

Now, the following command will add the certificate (where YOUR_FILE is your exported file):

certutil -d sql:$HOME/.pki/nssdb -A -t "P,," -n YOUR_FILE -i YOUR_FILE

To list all your certificates, run the following command:

certutil -d sql:$HOME/.pki/nssdb -L

If it still doesn't work, you could be affected by this bug: Issue 55050: Ubuntu SSL error 8179

P.S. Please also make sure that you have libnss3-tools, before you can use above commands.

If you don't have, please install it by:

sudo apt-get install libnss3-tools # on Ubuntu
sudo yum install nss-tools # on Fedora, Red Hat, etc.

(Source: https://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate)

Unfortunately Firefox still uses its own keychain and does not work.

Reasons

Kyma can run on windows and linux and we should cover all installation steps for them, including trusting kyma.local certificate

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

We need to unify key length on local and cluster installation (local CI certificate uses 2048 bits key whereas on cluster the key length is 4096).

Expected result

• Update the default certificate and key (4096) on minikube
• consider clean up in SingWithCA function ; we set some fields (e.g. Signature, PublicKey) in x509.Certificate structure which are ignored by x509.CreateCertificate function
• Consider switching from comas to slashes in the subject

Actual result

Key algorithm specified in the response is rsa2048

Steps to reproduce

• The key lengths can be checked using Open SSL

A user can provision a service instance for a remote environment that hasn't been mapped to the namespace yet.

It would be better from a user experience point of view if we disisable the Service Classes in Service Catalog if the Remote Environment has not been mapped to the namespace with some message/status on the class showing the reason for it being disabled.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Dear Colleagues,
the /v1/events API of the Application Connector returns content "type text/plain; charset=utf-8" for the following content: {"event-id":"a1832d05-3892-472f-87b3-ad0e0ccb5220"}

It should be application/json.

Cluster is playground.

Cheers

Andreas

Expected result

Content Type application/json.

Actual result

Content Type text/plain; charset=utf-8

Steps to reproduce

Call /v1/events API of the Application Connector

Troubleshooting

Ignore the Response (as Spring Boot does not do deserialization as expected)

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

All links in the last paragraph of docs/kyma/docs/001-overview.md are broken which is caused by the surrounding <p class="internal"> .. <p> HTML element

Expected result

markdown links should be rendered as links

Actual result

links in last paragraph are broken

Steps to reproduce

open https://github.com/kyma-project/kyma/blob/master/docs/kyma/docs/001-overview.md

Troubleshooting

Remove the surrounding <p class="internal"> .. <p> HTML element

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
After updating content of kyma/resources/helm-broker-repo/bundles directory I want to update repository by executing sync-bundles.sh script from kyma/resources/helm-broker-repo/development directory.

Expected result

Repository and index.yaml visible via web server is updated. No error messages are shown.

Actual result

"bundles does not exists" error message is shown, repo is not updated.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

• Getting started type of doc
• CLI way of registering a broker
• In case there is some more overarching explanation of the brokers missing, add Details documents
• Use best the same broker as we use for tests: [https://github.com/kyma-project/kyma/tree/master/tests/ui-api-layer-acceptance-tests/domain/servicecatalog/testdata/charts/ups-broker]

Reasons

We need clear documentation that explains how to register new broker in the catalog and how the classes definitions should look like so they are nicely displayed in the catalog UI

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
lambdatest-0.0.1.zip
Problem can be reproduced with example bundle above.

There is a strange problem with Helm Broker - when it is used to do the deploy using Service Catalog on UI - lambda function is created, but no deployment/pods are created based on it. However, when same chart definition is deployed using helm install in terminal everything works correctly, after function resource is created also deployment and pod are present on cluster. We experienced this problem both locally and on real cluster. I haven't noticed any information what could go wrong in logs.

Confirm these statements before you submit the issue:

• [ Y] I have searched open and closed issues for duplicates.
• [ Y] I have read the contributing guidelines.

Description

Introduces authentication and authorization for GraphQL.

Reasons

The GraphQL facade caches resources and does not forward every request to the API Server. So, the user token is not validated against RBAC. The consequence is that all authenticated users can perform all operations supported by the GraphQL facade. This is a vulnerability.

To patch this vulnerability, Kyma developers need an additional authorization layer before the GraphQL facade.

Attachments

More information about the change has been described in the following ADR: https://github.com/kyma-project/community/blob/master/architecture-decision-records/adr-015-Authorization_for_GraphQL.md

See screenshot

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

ServiceBindingUsage in deployments.

When i bind 2 service instances (which exposes GATEWAY_URL env variable) to any deployment the aforementioned env variable get overridden by the latter one.

Local Kyma installation sourced up via master branch

Expected result

I'd like to access the gateway urls exposed via both the service instances within the deployment Pods

Actual result

GATEWAY_URL env variable get overridden by the latter binding.

Steps to reproduce

1. Create two Service Catalog entries using https://gateway.kyma.local/hmc-default/v1/metadata/services pointing to 2 different destinations or APIs
2. Create a Service Instance and Bind it to any deployment inside your kyma installation for convenience please use the below deployment.yaml file

apiVersion: v1
kind: Service
metadata:
  name: sampleonkyma
  labels:
    application: sampleonkyma
  annotations:
    auth.istio.io/8080: NONE
spec:
  ports:
  - name: http
    port: 8080
  type: NodePort
  selector:
    application: sampleonkyma
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: sampleonkyma
spec:
  replicas: 1
  template:
    metadata:
      labels:
        application: sampleonkyma
      annotations:
        sidecar.istio.io/inject: "true"
    spec:
      containers:
      - image: acjoshi/kymagateway
        imagePullPolicy: Always
        name: sampleonkyma
        ports:
        - name: http
          containerPort: 8080
---
apiVersion: gateway.kyma.cx/v1alpha2
kind: Api
metadata:
  name: sampleonkyma
spec:
  hostname: appongateway.kyma.local
  service:
    name: sampleonkyma
    port: 8080

Try to read env variable from the "sampleonkyma" container

or execute "curl https://appongateway.kyma.local/hello/getGatewayURL"

Troubleshooting

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Dear Colleagues,

after a new cluster was setup, I was setup only as user. Hence I was getting a 403 error everywhere in the console which was good. However when browsing the Administration menu I could still see Service Brokers and Remote Environments (including a working 1 click connect).

Can you check this behavior?

Cheers

Andreas

Expected result

User receives 403

Actual result

User was able to browse Service Brokers and Remote Environments

Steps to reproduce

Remove Administrative Permission from user and go to Administration in Cluster

Troubleshooting

N/A

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

• Make sure serviceInstanceEvent works
• Once #180 is completed we need to add one parameter to UI API Virtual Service definition: websocketUpgrade: true
• Add 2 new subscriptions for ServiceBinding and ServiceBindingUsage that we will use in views where these resources are listed and their statuses exposed, in the ServiceInstance details view
• Acceptance tests for subscriptions

Reasons

Backed must support websockets to enable UI to do realtime updates of changes in the resources, like their status changes

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

I tried deploying the below yaml specs locally

apiVersion: v1
kind: Service
metadata:
  name: mkt-kyma
  namespace: stage
  labels:
    application: mkt-kyma
  annotations:
    auth.istio.io/8080: NONE
spec:
  ports:
  - name: http
    port: 8080
  type: NodePort
  selector:
    application: mkt-kyma
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: mkt-kyma
  namespace: stage
  annotations:
    sidecar.istio.io/inject: "true"
spec:
  replicas: 1
  template:
    metadata:
      labels:
        application: mkt-kyma
    spec:
      containers:
      - image: acjoshi/mkt-kyma
        imagePullPolicy: Always
        name: mkt-kyma
        ports:
        - name: http
          containerPort: 8080
---
apiVersion: gateway.kyma.cx/v1alpha2
kind: Api
metadata:
  name: mkt-kyma
spec:
  hostname: playsdk.kyma.local
  service:
    name: mkt-kyma
    port: 8080

Unfortunately https://playsdk.kyma.local doesn't exposes the API as expected

MacOsx, minikube deployment

Expected result

I'd like to see the docker image exposed via the API gateway

Actual result

i get an error saying: playsdk.kyma.local is currently unable to handle this request.
HTTP ERROR 503
Steps to reproduce

Just Deploy the yaml specs from Kyma Console and ensure the stage namespace is available

Troubleshooting

1. i tried getting inside the container using kubectl exec and ran the curl command on http://localhost:8080 to check if the application is running in the kubernetes pod which was created by kyma, i get the expected results
2. i added the host entry playsdk.kyma.local

Regards,
Anish Joshi

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Not all pods are created during installation in Windows 10 Home.

Expected result

Kyma instance accessible via https://console.kyma.local/

Actual result

Kyma not installed

Steps to reproduce

Here are the steps I've taken to install it locally:

1. Download kubectl, minikube, jq, and helm
2. Add location to PATH
3. Clone repository
4. Add certificate to trusted certificates following the steps in this link: https://www.thewindowsclub.com/manage-trusted-root-certificates-windows
5. Modified value of VM_DRIVER in scripts to virtual box or Execute .\cmd\run.ps1 -vm_driver virtualbox

Troubleshooting

1. To verify installation, I've executed: kubectl get pods --all-namespaces

PS C:\Kyma\kyma\installation> kubectl get pods --all-namespaces
NAMESPACE        NAME                                    READY     STATUS    RESTARTS   AGE
kube-system      kube-addon-manager-minikube             1/1       Running   0          2m
kube-system      kube-dns-6dcb57bcc8-c9lxh               3/3       Running   0          1m
kube-system      kubernetes-dashboard-5498ccf677-28wx5   1/1       Running   0          1m
kube-system      storage-provisioner                     1/1       Running   0          1m
kube-system      tiller-deploy-5b945b8b89-cnnkh          1/1       Running   0          1m
kyma-installer   kyma-installer-6bc6956958-ft6nc         1/1       Running   0          38s

2. Running is-installed script gives:

PS C:\Kyma\kyma\installation> .\scripts\is-installed.ps1
Checking state of kyma installation...hold on
kyma installation error... Installing cluster prerequisites
----------
Error: unknown command "pods" for "kubectl"

Did you mean this?
        logs

Run 'kubectl --help' for usage.
unknown command "pods" for "kubectl"

Did you mean this?
        logs

error: expected 'logs (POD | TYPE/NAME) [CONTAINER_NAME]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples.

3. Before each attempt, clean-up script is executed but error is encountered:

PS C:\Kyma\kyma\installation> .\scripts\clean-up.ps1
installation.installer.kyma.cx "kyma-installation" deleted
namespace "kyma-installer" deleted
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error: incompatible versions client[v2.10.0] server[v2.8.2]
Error from server (NotFound): namespaces "kyma-system" not found
Error from server (NotFound): namespaces "istio-system" not found
Error from server (NotFound): namespaces "kyma-integration" not found

So, I execute minikube delete and delete .minikube and .kube directories before I start a new installation attempt

4. Already pulled latest tag, but result of using the master branch is the same.

Here is the current discussion for the issue in the Slack channel: https://kyma-community.slack.com/archives/CBLBESMST/p1534903293000100

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
Incorrect error handling in ui-api-layer component.

Losing the error context

When we are creating/deleting objects in services then we are inlining the k8s command and returning the same error, see: https://github.com/kyma-project/kyma/blob/master/components/ui-api-layer/internal/domain/servicecatalog/instance_service.go#L186

This is not a good idea, because we are losing the context of given error, because of that, we should check if the error occurred and if yes, then wrap it with errors.Wrap()
Example

func (svc *instanceService) Create(params instanceCreateParameters) (*v1beta1.ServiceInstance, error) {
   // function body...
  err := svc.client.ServicecatalogV1beta1().ServiceInstances(params.Namespace).Create(&instance)
  if err != nil {
    return errors.Wrapf(err, "while creating service instance %q", instance.Name)
  }
  return nil
}

Relying directly on k8s errors

When we will introduce changes mention above then we need to also handle somehow the cases where we already rely on errors returned directly from k8s, e.g. see:
https://github.com/kyma-project/kyma/blob/master/components/ui-api-layer/internal/domain/servicecatalog/binding_resolver.go#L40

this problem can be solved by returning our own not found/already exists error and provide a function for detecting them: IsNotFound/IsAlreadyExists

Lack of correct recognition of errors

Not all mutations have implemented a proper error handling. We should always return a different error in case of already exists and not found err to help the end user to investigate the problem with the mutation failed. Now if any error occur then we are always returnig general error

"Cannot create instance `%s` in environment `%s

see:
https://github.com/kyma-project/kyma/blob/master/components/ui-api-layer/internal/domain/servicecatalog/instance_resolver.go#L38-L42

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

When you deploy Kyma locally, two files related to certificates are created. I would suggest to add those files to the .gitignore file in the root folder. At least for me it is annoying when trying to contribute to Kyma as a developer.

The page loading can be slow at times. In particular the page displaying the list of lambda functions is slow. It often takes 10-20s to load the page

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Check how we do it:

• this way? something like this: https://kubernetes.io/docs/reference/kubectl/cheatsheet/
• or simply CLI reference for each component and then aggregated view?
• or maybe part of devops docs that we do not have yet?
• partner reported troubles with simple java service, they needed to tweak the deployment manifest to get it working

For a simple spring boot app, the partner needed to set

• that settings in the entrypoint of the Dockerfile:
  {code}ENTRYPOINT ["java", "-XX:+UnlockExperimentalVMOptions", "-XX:+UseCGroupMemoryLimitForHeap", "-jar", "/project.jar"]{code}
• a memory resource request in the deployment manifest of 512Mi

Other interesting debug topics:

1. check if your pod is running healthy (having no frequent restarts recently)
2. try to directly connect to the pod internally by port forward and check the functionality of the service
3. how to debug envoy and trace the incoming request

Please also cover typical problems when installing kyma local. Especially outline what are the restrictions on using a local installation

Reasons

Provide cheat cheets and/or troubleshooting documents covering experience/best practice from our side on daily routines mainly around debugging. Can also cover points like list of typical resources you need to deal with. Just think of your personal notepad, what commands you wrote down (go around and ask for them).

It would be useful to see detailed information about the remote environment CRD directly in the console e.g.

• host name
• gateway URL
• availability

It would also be helpful to be able to test the connectivity to a remote environment and get back a meaningful message if the connection failed

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

People deploying Kyma locally have to find the password for the test user in a file. In readme file currently path + filename is provided. I would suggest to write the password directly in the readme file or if this not desired provide a link to the file instead of the current approach.

We use green, grey and orange/red status icons (e.g. lambda list page) but it's not clear what they mean. We should add tool tips to explain what these mean.

Things we want to change:

• remove status bubbles and replace by colored text with tooltip for more detailed info (if available), see #145 (comment)
• status column moved to last column before "Actions" column

Identified views that are affected:

• /home/settings/remoteEnvs: move status
• /home/settings/serviceBrokers: move status
• /home/environments/production/deployments: move status
• /home/environments/production/replicaSets: move status
• /home/environments/production/pods: move status
• /home/environments/production/services: move status

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

• Switch in Kyma ingress controller to istio gateway, migrate existing ingress definitions to virtual services, create one default Gateway definition for Kyma.
• Update api-controller version.

Reasons

In istio 0.8 gateway was introduced as a replacement for ingress controller however, ingress is still supported but deprecated. In a future istio release, ingress controller will not be supported anymore, therefore we have to switch it in Kyma. Additionally, Gateway comes with VirtualService and new API.

Attachments

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Dear Colleagues,

after creating a new environment (according to https://kyma-project.io/docs/latest/components/application-connector#details-deploy-a-new-application-connector) the Remote environment always is in status not serving. This can only be resolved by restarting pod core-ui-api-* in namespace kyma-system. Please fix this.

Thanks

Andreas

Expected result

Environment appears as serving w/o restart

Actual result

Environment appears as not serving

Steps to reproduce

Deploy new remote environment via helm

Troubleshooting

restart core-ui-api-*

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

I have a lambda which is exposed over secured HTTP. I am fetching the token using Fetch token functionality in UI. The token is presented without the prefix Bearer.

The same functionality available in Service UI is returning token with the prefix Bearer.

Expected result

I would like to have the same experience using both functionalities for getting a token.

Steps to reproduce

• Create a lambda which is exposed
• Use the Fetch Token functionality

When events are not able to be processed (exception in the lambda function), the event sending is retried endlessly. Some strategy(ies) for handling backoff/retries are needed.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
There is no information about what branch/tag should be checked out to obtain tested/stable release in the documentation (main page or "Getting started" page). Users may (like us) assume that they can just use master branch, which may not be stable at given moment. Also some general information about release cycle should be useful.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Installation script fails for me on current master branch with error message:
/Users/i326235/kyma/github/kyma/installation/cmd/../scripts/installer.sh: line 61: unexpected EOF while looking for matching "'`

Older revisions (like dea7dd4) work fine.

Expected result

Kyma should install itself successfully

Actual result

KTWM33956433A:cmd i326235$ ./run.sh

################################################################################
# Minikube setup with driver hyperkit
################################################################################

E0802 11:04:51.289872    6200 status.go:85] Error cluster status: getting status: running command: sudo systemctl is-active kubelet
.: Process exited with status 3
Minikube is already initialized
Do you want to remove previous minikube cluster [y/N]: y
Deleting local Kubernetes cluster...
Machine deleted.
Parsing DEX TLS certificate secret...
Saving DEX TLS certificate in the container file: /Users/i326235/.minikube/files/dex-ca.crt...
DEX TLS certificate saved in the container: /Users/i326235/.minikube/files/dex-ca.crt
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
WARNING: The localkube bootstrapper is now deprecated and support for it
will be removed in a future release. Please consider switching to the kubeadm bootstrapper, which
is intended to replace the localkube bootstrapper. To disable this message, run
[minikube config set ShowBootstrapperDeprecationNotification false]
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Waiting for minikube to be up...
Keep calm, there are 15 possibilities and so far it is attempt number 1
Minikube is up
Minikube IP address: 192.168.64.59
Adding apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local  configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local to /etc/hosts on Minikube
127.0.0.1 apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local  configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local
Password:
Adding apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local  configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local to /etc/hosts on localhost
Domain added to /etc/hosts

Generating secret for Cluster certificate

Generating secret for Remote Environemnts

Generating config map for installation

Applying configuration
namespace/kyma-installer created
secret/remote-env-certificate created
secret/cluster-certificate created
configmap/installation-config created

Generating secret for UI Test

Applying asecret for UI Test
secret/ui-test created

################################################################################
# Kyma Installer setup
################################################################################

/Users/i326235/kyma/github/kyma/installation/cmd/../scripts/installer.sh: line 61: unexpected EOF while looking for matching `"'

Troubleshooting

I tried also with totally blank minikube, (after minikube stop, minikube delete and rm -rf ~/.minikube/), end result was the same.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Changes required:

• move components list from installer config-map to installation CR

• extend components list to support more descriptive installation steps

• componentName - required

• releaseName - default=componentName

• namespace - required

• stepType [helm, kubectl-apply, kubectl-patch]- default=helm

• installer will not support bash scripts execution

• installer will not support dependencies, if your component relies on another component then you need to handle dependency checking yourself (init containers)

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Dear Colleagues,

Kyma allows for event-driven extensibility. So far this feature is tightly coupled to the Application Connector (Binding, Event Registration, etc.). However I can see use cases where services running within the same Kubernetes cluster are also raising and consuming events themselves.

Reasons
To avoid the overhead (development complexity and runtime) of the application connector it would be cool to have a internal API as well.

Attachments

N/A

test - issue, please ignore/close

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Following local installation instructions on Mac. The output from cmd/run.sh looks fine (see below) but when I access the kyma console, I get issues. I log in with the default login and the console environments page shows Http failure response for (unknown url): 0 Unknown Error

Authorization requests for the following XHR calls fail:
https://apiserver.kyma.local/apis/ui.kyma.cx/v1alpha1/namespaces/undefined/microfrontends
https://apiserver.kyma.local/api/v1/namespaces?labelSelector=env=true

Kyma commit ad60bf8
Mac OSX 10.13.6
Chrome version 67.0.3396.99

Expected result

When accessing https://console.kyma.local I expect to see a list of default environments.

Actual result

Http failure response for (unknown url): 0 Unknown Error

Steps to reproduce

Install kyma per https://github.com/kyma-project/kyma/blob/master/docs/kyma/docs/031-gs-local-installation.md
Access https://console.kyma.local

Troubleshooting

I verified the prerequisite versions of all software described in installation instructions and I downgraded kubernetes-cli and minikube to the recommended versions.

Install output:
`C02W12JUHTD6:installation i839851$ cmd/run.sh

################################################################################

Minikube setup with driver hyperkit

################################################################################

Minikube is already initialized
Do you want to remove previous minikube cluster [y/N]: y
Deleting local Kubernetes cluster...
Machine deleted.
Errors occurred deleting mount process: os: process already finished
Parsing DEX TLS certificate secret...
Saving DEX TLS certificate in the container file: /Users/i839851/.minikube/files/dex-ca.crt...
DEX TLS certificate saved in the container: /Users/i839851/.minikube/files/dex-ca.crt
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
WARNING: The localkube bootstrapper is now deprecated and support for it
will be removed in a future release. Please consider switching to the kubeadm bootstrapper, which
is intended to replace the localkube bootstrapper. To disable this message, run
[minikube config set ShowBootstrapperDeprecationNotification false]
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Waiting for minikube to be up...
Keep calm, there are 15 possibilities and so far it is attempt number 1
Minikube is up
Minikube IP address: 192.168.64.17
Adding apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local to /etc/hosts on Minikube
127.0.0.1 apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local
Password:
Adding apiserver.kyma.local console.kyma.local catalog.kyma.local instances.kyma.local dex.kyma.local docs.kyma.local lambdas-ui.kyma.local ui-api.kyma.local minio.kyma.local jaeger.kyma.local grafana.kyma.local configurations-generator.kyma.local gateway.kyma.local connector-service.kyma.local to /etc/hosts on localhost
Domain added to /etc/hosts

################################################################################

Kyma Installer setup

################################################################################

namespace "kyma-installer" created
limitrange "kyma-default" created
resourcequota "kyma-default" created
customresourcedefinition "installations.installer.kyma.cx" created
customresourcedefinition "releases.release.kyma.cx" created
serviceaccount "kyma-installer" created
deployment "kyma-installer" created
clusterrole "kyma-installer-reader" created
clusterrolebinding "kyma-installer" created
clusterrolebinding "default-sa-cluster-admin" created
kube-dns is not deployed - waiting 5s...
kube-dns is deployed...
/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found
kube-dns-6dcb57bcc8-d2ngf is not running - waiting 5s...
/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found
kube-dns-6dcb57bcc8-d2ngf is not running - waiting 5s...
/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found
kube-dns-6dcb57bcc8-d2ngf is not running - waiting 5s...
/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found
kube-dns-6dcb57bcc8-d2ngf is not running - waiting 5s...
/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found
kube-dns-6dcb57bcc8-d2ngf is not running - waiting 5s...
kube-dns-6dcb57bcc8-d2ngf is running...
kubedns endpoint IP is not assigned yet - waiting 5s...
kubedns endpoint IP assigned

Generating secret for UI Test

Applying asecret for UI Test
secret "ui-test" created

Generating secret for Cluster certificate

Applying asecret for Cluster certificate
secret "cluster-certificate" created

Generating config map for installation
configmap "installation-config" created
Copying kyma sources from /SAPDevelop/kyma/kyma into kyma-installer-55cf6546dd-8p2rz:/kyma ...
kyma-installer is deployed...`

/SAPDevelop/kyma/kyma/installation/scripts/is-ready.sh: line 38: jq: command not found kyma-installer-55cf6546dd-8p2rz is not running - waiting 5s... kyma-installer-55cf6546dd-8p2rz is running... Applying CR for installer from path /SAPDevelop/kyma/kyma/installation/cmd/../../temp-V6VQjJD0KT/installer-cr-local.yaml installation "kyma-installation" created C02W12JUHTD6:installation i839851$ scripts/is-installed.sh Checking state of kyma installation...hold on Status: InProgress, description: Installing istio Status: InProgress, description: Installing istio Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Installing Prometheus operator Status: InProgress, description: Provisioning helm broker repo bundles Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Installing core Status: InProgress, description: Upgrading core Status: InProgress, description: Installing Hmc Remote Environment Status: InProgress, description: Installing Ec Remote Environment Status: InProgress, description: Installing Ec Remote Environment kyma is installed...

C02W12JUHTD6:installation i839851$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE istio-system istio-citadel-7bdc7775c7-pxgq5 1/1 Running 0 7m istio-system istio-egressgateway-c7c48c8d5-zbhkf 1/1 Running 0 7m istio-system istio-ingress-5f4f9d784d-gs6sc 1/1 Running 0 7m istio-system istio-ingressgateway-7d85554b57-6jmdz 1/1 Running 0 7m istio-system istio-pilot-9bcd4bd5f-426b2 2/2 Running 0 7m istio-system istio-pilot-9bcd4bd5f-ftdfj 2/2 Running 0 7m istio-system istio-policy-5bc7bb5f-2hdhs 2/2 Running 0 7m istio-system istio-sidecar-injector-645c89bc64-g6d9q 1/1 Running 0 7m istio-system istio-statsd-prom-bridge-6957c8bc7b-g4k2q 1/1 Running 0 7m istio-system istio-telemetry-74b49dc7f5-9qwt2 2/2 Running 0 7m istio-system istio-webhook-657b9c8cc8-z2wx4 1/1 Running 0 7m kube-system kube-addon-manager-minikube 1/1 Running 0 8m kube-system kube-dns-6dcb57bcc8-d2ngf 3/3 Running 0 8m kube-system kubernetes-dashboard-5498ccf677-hrxxp 1/1 Running 0 8m kube-system storage-provisioner 1/1 Running 0 8m kube-system tiller-deploy-5b945b8b89-4zq52 1/1 Running 0 8m kyma-installer kyma-installer-55cf6546dd-8p2rz 1/1 Running 0 8m kyma-integration connector-service-84bbc5784c-m76d2 2/2 Running 0 5m kyma-integration ec-default-gateway-9cd4b6ff4-98bkv 2/2 Running 0 1m kyma-integration hmc-default-gateway-7dd98586c7-4cc7m 2/2 Running 0 1m kyma-integration metadata-service-5d558f5668-ppndh 2/2 Running 0 5m kyma-system alertmanager-core-0 2/2 Running 0 5m kyma-system api-controller-67bc65b759-c58xg 1/1 Running 0 5m kyma-system configurations-generator-9d4bc9c65-2dtq4 2/2 Running 0 5m kyma-system core-binding-usage-controller-7d77fcdb8b-888kn 2/2 Running 0 5m kyma-system core-catalog-apiserver-6b5cc5766b-zwqsf 1/1 Running 1 5m kyma-system core-catalog-controller-manager-76ff798778-mncgd 1/1 Running 1 5m kyma-system core-catalog-ui-6f47647857-xk8pp 1/1 Running 0 5m kyma-system core-console-79d7cf5f56-rvszp 1/1 Running 0 5m kyma-system core-content-ui-84cbf4df4f-bm6xw 1/1 Running 0 5m kyma-system core-environments-746fcfbb9f-dp87b 1/1 Running 0 5m kyma-system core-etcd-0 1/1 Running 0 5m kyma-system core-exporter-kube-state-7b44c44dcd-bl5m7 2/2 Running 0 3m kyma-system core-exporter-node-rsx4h 1/1 Running 0 5m kyma-system core-grafana-0 2/2 Running 0 5m kyma-system core-helm-broker-6fb55f99dc-9944t 1/1 Running 0 5m kyma-system core-helm-broker-etcd-0 1/1 Running 0 5m kyma-system core-helm-broker-reposerver-7d4d9bd8cc-97p9g 1/1 Running 0 5m kyma-system core-instances-ui-784b897cc4-4fk8g 1/1 Running 0 5m kyma-system core-jaeger-78bf5b7c49-n4c2k 1/1 Running 0 5m kyma-system core-kubeless-controller-manager-5768b686b-fzbxj 1/1 Running 0 5m kyma-system core-lambdas-ui-779dbb4944-wgjgl 1/1 Running 0 5m kyma-system core-minio-686c985bbb-v58h7 1/1 Running 0 5m kyma-system core-nats-streaming-0 2/2 Running 0 5m kyma-system core-nginx-ingress-controller-567c5784c6-wm447 1/1 Running 0 5m kyma-system core-nginx-ingress-default-backend-78c79c7544-bzq87 1/1 Running 0 5m kyma-system core-publish-769f7fdb7d-7mk5t 2/2 Running 2 5m kyma-system core-push-54d48dd957-x98bf 2/2 Running 5 5m kyma-system core-remote-environment-broker-586c48cb8-gktjs 1/1 Running 5 5m kyma-system core-sub-validator-bc66bbfc5-jlstd 2/2 Running 0 5m kyma-system core-ui-api-5f7978c8fc-x6vps 2/2 Running 0 5m kyma-system dex-7b6548bdcc-5j46t 1/1 Running 0 5m kyma-system nginx-proxy-7db85955f6-6zzsm 3/3 Running 0 5m kyma-system prometheus-core-0 2/2 Running 0 5m kyma-system prometheus-operator-57b98966c7-gn54s 1/1 Running 0 6m

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

https://github.com/kyma-project/kyma/blob/master/docs/kyma/docs/042-gardener-kyma-deployment.md is not true, you cannot install kyma and test it on gardener without any issues and have full kyma support.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

I simply created a small lambda function from the console UI after Kyma Installation process, given the point of entry as http, i tried accessing the lambda via HTTP endpoint, Unfortunately it fails with status ERR_NAME_NOT_RESOLVED

Kubernetes version: 1.11.1, locally deployed minikube, cloned from master, macosx
Expected result

Lambda function created should be accessible via HTTP endpoint

Actual result

Site not reachable with status ERR_NAME_NOT_RESOLVED

Steps to reproduce

i just followed the local installation guide and tried creating a lambda followed by accessing it.

Troubleshooting

Unfortunately New to this, hence not sure how to troubleshoot, sorry

Regards,
Anish

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
provision-bundles.sh script used during Helm Broker Repository synchronisation assumes that pod defined in po.yaml will be deployed to same node as core-helm-broker-reposerver as it requires to share same PersistentVolumeClaim. This may not happen in multi-node cluster setup - bundles-repository-provisioner will fail to start in this case and will stay in broken state.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
I exposed a lambda using the "Create API" button on APIs page. I checked the "Secure API" checkbox.
However, the response code is "200 OK" when I call the API.

On the other hand, authorization is working if I expose a lambda by selecting "HTTP - Endpoint" as a function trigger.

Steps to reproduce
*Create lambda
*Expose the lambda as a secured API on APIs page
*Call endpoint without token

I think it makes more sense to stay on the lambda function editor page after saving the function. It is inconvenient to have to reopen the editor each time to make a change.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description
After installing Kyma successfully on the local machine, I retrieved a certificate from Kyma. However, metaDataUrl and eventsUrl endpoints are not reachable, because the port was not specified. They are accessible after defining the port. They should be represented including the port in the response while retrieving the certificate.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

OSBA provides the following convention for imageUrl: https://github.com/openservicebrokerapi/servicebroker/blob/31bf79dd3b6573d8959940c01e4460ac33d33cb5/profile.md#service-metadata-fields

We should use that one in Helm Broker, and not expect ui-api-layer component reads both, imageUrl and imageURL for example.

Expected result

metadata.imageUrl
metadata.documentationUrl

Actual result

metadata.imageURL
metadata.documentationURL

When making any changes on the lamdba function editor page, it would be helpful to the developer if we gave them a warning if they try to leave the page without saving the changes. A number times I have added environment variables and forgot to save the changes

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Quoting suggested refactoring points by @akgalwas (reference: #182):

In components/event-gateway/internal/events/bus/process.go:9

I'm not certain what is the purpose of using pointer here, I think it adds some complexity. In main.go "&" operator is used to pass string's pointer to bus.Init. In bus.Init configurationData members are set but in AddSource * operator is used to dereference the pointer. I think bus.Init and configurationData could use string instead of *string (passing by value is more natural here).

In components/event-gateway/internal/events/bus/send.go:26

I would propose to refactor this function a bit. I would extract the following operations into separate functions : creating http request, unmarshaling correct response, unmarshalling error response. Such a change would make SentEvent shorter and easier to read. What do you think?

In components/event-gateway/internal/events/bus/process.go:15

I would avoid global variables. Consider declaring struct (e.g. EventBus) with configuration and eventTargetURL properties. Init function would be a factory method and return the struct (or an interface if you would like to mock it). What do you think?

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

This
should most probably go here as we need clear security documentation. We would also probably need some general section about this in the overarching kyma docs

 other ideas? I'm all ears

Reason

Security applied on graphql layer that serves as catalog ui backend must be visible in official docs set

The logging ui should be integrated smoothly into the existing pod and lambda views. Investigate how that can be achieved having in mind that the logging ui might be optional. And apply it.

AC:

• Propose a way how to integrate the view (for example by adding a new option to the actions dropdown) and apply it.
• Assure that the integration can be done dynamically (for example the action is configured by the log UI and will be displayed only if installed)

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Make sure content from:

• https://github.com/kyma-project/kyma/tree/master/resources/core/charts/monitoring/charts/grafana
• https://github.com/kyma-project/kyma/tree/master/resources/core/charts/monitoring/charts/alert-rules
• https://github.com/kyma-project/kyma/tree/master/resources/core/charts/monitoring/charts/alertmanager

is actually a part of https://github.com/kyma-project/kyma/tree/master/docs/monitoring/docs

Reasons

There are details that should be well described and visible to Kyma users so they know how to operate Kyma components and also expose their own metrics

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Exposed environment variables on service include non bound services

• I have a deployed service that i use to test.
• There is redis instance this service is bound to.
• There are a bunch of other redis service instances in the environment in kyma, but these instances are not bound to the service.

Environment: playground (stage)

Expected result
I have expected to only see environment variables populated from the bound instance.

Actual result
I see environment variables of the bound instance and all other instances in that namespace.

Examples of these environment variables are:

HB_REDIS_ENTERPRISE_21DF9909_A116_11E8_AAE7_BE3F5F456_REDIS_PORT_6379_TCP=tcp://10.0.138.50:6379
HB_REDIS_ENTERPRISE_21DF9909_A116_11E8_AAE7_BE3F5F456_REDIS_PORT_6379_TCP_ADDR=10.0.138.50
HB_REDIS_MICRO_2632847B_9FC8_11E8_AAE7_BE3F5F4569CB_REDIS_SERVICE_HOST=10.0.86.94
HB_REDIS_MICRO_393D11CC_9FAB_11E8_BAC0_BE3F5F4569CB_REDIS_SERVICE_PORT_REDIS=6379
HB_REDIS_MICRO_393D11CC_9FAB_11E8_BAC0_BE3F5F4569CB_REDIS_PORT_6379_TCP_PROTO=tcp
HB_REDIS_MICRO_393D11CC_9FAB_11E8_BAC0_BE3F5F4569CB_REDIS_PORT_6379_TCP_ADDR=10.0.33.215
HB_REDIS_MICRO_2632847B_9FC8_11E8_AAE7_BE3F5F4569CB_REDIS_SERVICE_PORT_REDIS=6379
HB_REDIS_MICRO_2632847B_9FC8_11E8_AAE7_BE3F5F4569CB_REDIS_PORT=tcp://10.0.86.94:6379
HB_REDIS_MICRO_2632847B_9FC8_11E8_AAE7_BE3F5F4569CB_REDIS_PORT_6379_TCP_ADDR=10.0.86.94
HB_REDIS_MICRO_393D11CC_9FAB_11E8_BAC0_BE3F5F4569CB_REDIS_PORT_6379_TCP=tcp://10.0.33.215:6379
HB_REDIS_MICRO_2632847B_9FC8_11E8_AAE7_BE3F5F4569CB_REDIS_SERVICE_PORT=6379
HB_REDIS_ENTERPRISE_21DF9909_A116_11E8_AAE7_BE3F5F456_REDIS_SERVICE_PORT=6379
HB_REDIS_ENTERPRISE_21DF9909_A116_11E8_AAE7_BE3F5F456_REDIS_PORT=tcp://10.0.138.50:6379
HB_REDIS_MICRO_393D11CC_9FAB_11E8_BAC0_BE3F5F4569CB_REDIS_SERVICE_PORT=6379

Update the component event-bus charts version 0.2.13 to be consistent with the tests event-bus published docker images

There is no indication on the lambda functions page when a function/pod crashes and fails to deploy

A status column similar to the pods list page would help here.

Confirm these statements before you submit the issue:

• I have searched open and closed issues for duplicates.
• I have read the contributing guidelines.

Description

Application Connector documentation contains a broken link to remote-environments.zip file.
This file doesn't exist and is not needed anymore.

Expected result

The documentation describes how to install Remote Environment with use of GitHub repository.

Steps to reproduce

• Open following link https://github.com/kyma-project/kyma/blob/master/docs/application-connector/docs/010-details-ac-deployment.md#install-an-application-connector-on-the-cluster
• Use the search function to find .zip