Description
Please see errors in the recent builds and fix.

Recent builds - https://github.com/layer5io/meshery-kuma/actions

Example of error - https://github.com/layer5io/meshery-kuma/pull/18/checks?check_run_id=257153915#step:4:1

Current Situation
The ReleaseDrafter utility (GitHub Action) is not configured in this repository.

Desired Situation

• Releasedrafter should be configured to execute whenever a PR is merged to master in this repo.

Implementation

• Copy the releasedrafter config and the releasedrafter workflow file from the meshery repo and place in the .github folder here.

Screenshots

Description
The CI in this repo needs updated to follow new Layer5 practices.

See https://github.com/layer5io/meshery-kuma/runs/1295491967?check_suite_focus=true for details

Description
Unaddressed issues that remain open for long periods may be automatically marked stale and closed.

Implementation
Copy stale.yml from the Meshery repo and put into the .github folder here.

Yes right, let me craete a helm chart for this, so that we can version them too.

Originally posted by @kumarabd in #71 (comment)

Logs

app=kuma-adaptor ts=2020-12-19T00:50:26.13048218Z caller=level.go:63 level=error code=1001 severity=1 short-description=None long-description="Error creating adapter instance.Error validating kubeconfig.open /Users/lee/.minikube/profiles/minikube/client.crt: no such file or directory" probable-cause=None suggested-remediation=None code=1001 severity=1 short-description=None long-description="Error creating adapter instance.Error validating kubeconfig.open /Users/lee/.minikube/profiles/minikube/client.crt: no such file or directory" probable-cause=None suggested-remediation=None

Expected Behavior
Upgrade to meshkit v0.1.30

@Aisuko The changes look good. Will you be able to address to the static checks? They are mostly just comments which are missing.

No problems.

Originally posted by @Aisuko in #142 (comment)

Description
The Kuma project no longer publishes its binaries on bintray, which is causing the Meshery Adapter for Kuma to fail to install Kuma.

Screenshots

Thank you for today’s demo, @kumarabd. Before merging, will you attend to each of the failed build checks?

Originally posted by @leecalcote in #71 (comment)

Description

Description

README.md is the first file one should read when starting a new project. For attractive look, we added some badges also.
But, there's a Slack badge failing, need to fix that.

Example Screenshot

Current Behavior

Desired Behavior

Environment:

• OS: any [e.g. Ubuntu]
• Browser: any [e.g. Chrome, Safari]
• Version: any [e.g. 22]
• Device: any [e.g. laptop, iPhone 8]

Description
Adapter initialisation fails with meshery. Below are the logs:

time="2021-04-05T21:36:32Z" level=info msg="Adaptor Listening at port: 10007" app=kuma-adaptor
time="2021-04-05T21:39:05Z" level=info msg="Creating instance" app=kuma-adaptor
time="2021-04-05T21:39:05Z" level=error msg="Error creating adapter instance.Error validating kubeconfig.none of the auth infos are valid either the certificate path is invalid or is inaccessible" app=kuma-adaptor code=1001 probable-cause=None severity=1 short-description=None suggested-remediation=None

Enviroment:

• OS: [e.g. Ubuntu]
• Browser: [e.g. Chrome, Safari]
• Version: [e.g. 22]
• Device: [e.g. laptop, iPhone 8]

[Optional] To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

[Optional] Additional Context
Add any other context about the problem here.

Current Behavior
A brief description of what the problem is. (e.g. I need to be able to...)

Desired Behavior
A brief description of the enhancement.

[Optional] Alternatives
A brief description of any alternative solutions or features you've considered.

[Optional] Additional context
Add any other context or screenshots about the feature request here.

Current Behavior
Port meshkit errors to the new error utility function. Instructions covered here, meshery/meshkit#48

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

vbom.ml/[email protected]: unrecognized import path "vbom.ml/util" (https fetch: Get https://vbom.ml/util?go-get=1: EOF)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Description

Whenever installation option is chosen in adapter it terminates with the error

usage: grep [-abcDEFGHhIiJLlmnOoqRSsUVvwxZ] [-A num] [-B num] [-C[num]]
	[-e pattern] [-f file] [--binary-files=value] [--color=when]
	[--context[=num]] [--directories=action] [--label] [--line-buffered]
	[--null] [pattern] [file ...]

Expected Behavior

The adapter should be able to provision operations correctly.

Enhancement Description

To generate the workflow of getting the manifest from the KUMA using the kubeopenapi-jsonschema to read and generate json schemas from those manifests and then also generating workload definitions from those schemas.

A sample workflow is here

Description
A brief description of the issue.

Expected Behavior
A brief description of what you expected to happen.

Screenshots
Add screenshots, if applicable, to help explain your problem.

Enviroment:

• OS: [e.g. Ubuntu]
• Browser: [e.g. Chrome, Safari]
• Version: [e.g. 22]
• Device: [e.g. laptop, iPhone 8]

[Optional] To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

[Optional] Additional Context
Add any other context about the problem here.

link to new welcome guide (https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit#)

Current Behavior
A welcome bot has been configured to usher in contributors new to this project. However, a reminder to star the project is missing in the message.

Desired Behavior
The config.yml should be updated, you can take a cue from the highlighted line 22

[Optional] Alternatives
A brief description of any alternative solutions or features you've considered.

[Optional] Additional context
Add any other context or screenshots about the feature request here.

Screenshots

Enviroment:

• Meshery Version: v0.5.0

Current Behavior
A brief description of what the problem is. (e.g. I need to be able to...)

There is not has any cached to do this and can cause we install Kuma failed.

Desired Behavior
A brief description of the enhancement.

Even though bintray was outage, we can install the latest version of Kuma that meshery supports.

[Optional] Alternatives
A brief description of any alternative solutions or features you've considered.

[Optional] Additional context
Add any other context or screenshots about the feature request here.

Description
Fix CI security issues for the adapter code. Right now this is being passed. These are:

1. Dynamic argument value in http.Get() method
2. Dynamic argument parameter in the Cmd() method

Description

README.md is the first file one should read when starting a new project. Our community launched Discussion forum for help seekers; needs to publish it officially on README.md for convenience.

Screenshots

Current behaviour:

Desired behaviour:

Note:
Need to add only last line for Community Forum

Environment:

• OS: any [e.g. Ubuntu]
• Browser: any [e.g. Chrome, Safari]
• Version: any [e.g. 22]
• Device: any [e.g. laptop, iPhone 8]

Reference:

• Take reference to this pull request

Description
The following operation should be named "Delete Kuma service mesh"

Expected Behavior

1. Use "Delete", not "Install"
2. Capitalize "Kuma"

Description
See https://github.com/layer5io/meshery-kuma/pull/139/checks?check_run_id=2141506683#step:4:21

Current Behavior
The Meshery adapter for Kuma has not been included into the default Meshery release as a beta adapter, yet.

I haven't seen the Kuma adapter in-action as a container, yet, and so I'm not sure if this has already been addressed.

Desired Behavior
The Meshery adapter for Kuma should display a Kuma project logo on the adapter chip in the Meshery UI. Code changes will need to be completed in Meshery to ensure proper representation.

Description
Recent changes to the Meshery adapter for Kuma are producing a large container image size.

Expected Behavior
This adapter's container image size should be between 30MB to 90MB.

The module path github.com/layer5io/gokit found in your go.mod doesn't match the actual path github.com/layer5io/meshkit found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/layer5io/meshkit should resolve this issue.

View the update logs.

Description
This repo's readme needs the layer5 logo added to the .github folder (see other layer5io repos for an example) and the readme updated to point to the local copy of this logo image.

Description
Some of the badges in this repos readme are missing informative hyperlinks.

Desired Behavior
The badges (and their links) that are used in the Meshery repo's README are a great example of how the badges in this repo can be improved.

Enhancement Description
Pull-in GitHub Actions from another adapter. Update as needed to ensure that the checks and build are happening.

Current Situation
New contributors to this repo should be celebrated. A portion of this celebration can be automated.

Desired Situation
We can use a GitHub bot to do this. The config.yml, welcome folder and welcome image can be copied (and updated) from the the Meshery repo and placed into the .github folder in this repo.

Current Behavior
See meshery/meshery#1270 for additional details and the meshery/meshery#284 epic.

Desired Behavior
Implement in the same fashion that has been done in layer5io/meshery repo.

Description
The Community section in the README says "Access the Community Drive". There is a new procedure of having this automated based on the individual filling in a community member form

Expected Behavior
Update "Access Community Drive" to "To Access Community Drive, fill Community Member Form"

Screenshots

Enviroment:

• OS: [e.g. Ubuntu]
• Browser: [e.g. Chrome, Safari]
• Version: [e.g. 22]
• Device: [e.g. laptop, iPhone 8]

Description
Kuma fails to install.

Environment
Meshery v0.4.6

logs

eshery-kuma_1      | {"level":"info","msg":"Installing Kuma","time":"2020-09-22T21:27:10Z"}
meshery-kuma_1      |   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
meshery-kuma_1      |                                  Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 54.8M  100 54.8M    0     0  6975k      0  0:00:08  0:00:08 --:--:-- 8013k
meshery-kuma_1      |
meshery-kuma_1      | INFO	Kuma 0.7.0 has been downloaded!
meshery-kuma_1      |
meshery-kuma_1      | namespace/kuma-system unchanged
meshery-kuma_1      | secret/kuma-sds-tls-cert configured
meshery-kuma_1      | secret/kuma-kds-tls-cert configured
meshery-kuma_1      | secret/kuma-admission-server-tls-cert configured
meshery-kuma_1      | configmap/kuma-control-plane-config unchanged
meshery-kuma_1      | serviceaccount/kuma-control-plane unchanged
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/circuitbreakers.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/dataplaneinsights.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/traffictraces.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/zones.kuma.io unchanged
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/zoneinsights.kuma.io unchanged
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/dataplanes.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/faultinjections.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/healthchecks.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/meshes.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/proxytemplates.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/trafficlogs.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/trafficpermissions.kuma.io configured
meshery-kuma_1      | customresourcedefinition.apiextensions.k8s.io/trafficroutes.kuma.io configured
meshery-kuma_1      | clusterrole.rbac.authorization.k8s.io/kuma:control-plane unchanged
meshery-kuma_1      | clusterrolebinding.rbac.authorization.k8s.io/kuma:control-plane unchanged
meshery-kuma_1      | role.rbac.authorization.k8s.io/kuma:control-plane unchanged
meshery-kuma_1      | rolebinding.rbac.authorization.k8s.io/kuma:control-plane unchanged
meshery-kuma_1      | Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "service.validator.kuma-admission.kuma.io": Post https://kuma-control-plane.kuma-system.svc:443/validate-v1-service?timeout=30s: service "kuma-control-plane" not found
meshery-kuma_1      | ERROR	Unable to apply manifests
meshery-kuma_1      | ERROR	Unable to deploy
meshery-kuma_1      | {"code":"Kuma installation failed","level":"error","msg":"Error installing mesh: exit status 1","time":"2020-09-22T21:27:19Z"}
meshery-kuma_1      | {"code":"Sending error event","level":"error","msg":"Error installing mesh: exit status 1","time":"2020-09-22T21:27:19Z"}

Description
Running Meshery locally and Kuma Adapter locally. When Meshery Server connects the following bug is seen:

Logs

DEBU[0083] meshLocationURL: mesherylocal.layer5.io:10010 
DEBU[0083] created client for adapter: mesherylocal.layer5.io:10010 
DEBU[0083] retrieved supported ops for adapter: mesherylocal.layer5.io:10010 
ERRO[0083] Error getting service mesh name.: rpc error: code = Unimplemented desc = unknown method ComponentInfo for service meshes.MeshService 

Enviroment:

• Version: v0.5.5

Description
A brief description of the issue.

As @leecalcote said, that the Meshery adapter for Kuma is 300MB currently,

Expected Behavior
A brief description of what you expected to happen.

We need to cut down the adapter size to 30MB

Screenshots
Add screenshots, if applicable, to help explain your problem.

Enviroment:

• OS: [e.g. Ubuntu]
• Browser: [e.g. Chrome, Safari]
• Version: [e.g. 22]
• Device: [e.g. laptop, iPhone 8]

[Optional] To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

[Optional] Additional Context
Add any other context about the problem here.

The module path github.com/layer5io/gokit found in your go.mod doesn't match the actual path github.com/layer5io/meshkit found in the dependency's go.mod.

Updating the module path in your go.mod to github.com/layer5io/meshkit should resolve this issue.

View the update logs.

Issue Description
Create contributing.md that points to the central contributing.md in the Meshery repo.

Create a stub CONTRIBUTING.md in each of the repos that essentially say:
“You want to contribute to the project? Yay! We want you to! Visit our centralized instructions for contributing.", where the “contributing” is a hyperlink to the CONTRIBUTING.md in the main meshery repo.

Future Effort
In time, as more contributors join the project, we may need a meshery-community repo that has all this and much more info or to have a community / contributing section in the meshery docs.

Description
See build failure here - https://github.com/layer5io/meshery-kuma/runs/1029727524?check_suite_focus=true#step:5:28

Description
This Kuma adapter was built using the Istio adapter as a template. The Kuma adapter build is failing given that some of the Istio code remains.

Build failure - https://github.com/layer5io/meshery-kuma/runs/279301685#step:4:119

Expected Behavior
The Istio references need changed or removed. Kuma adapter should build cleanly.

Description
Prepare repo for building Kuma adapter.

Implementation

• new docker hub repo
• swap Istio with Kuma
• update go packages

Current Behaviour
Error codes utility runner workflow is not present.

Desired Behavious
Add the error codes utility runner workflow.

Instructions in meshery/meshery-linkerd#213