What negative ramifications are involved in removing the “v1“? Any? If not, please do.

Originally posted by @leecalcote in #120 (comment)

Description
MeshSync doesn't discover this resource type.

Expected Behavior
Add support for discovering ConfigMap Kubernetes resource type. Do the same thing that was done here - 1b640b8, but for ConfigMap

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Description
A couple of broken images appear at the bottom of this repo's readme.

Expected Behavior
These image should be stored and referenced locally in the meshsync repo - https://github.com/layer5io/meshsync/tree/master/.github/readme/images

Screenshots

Description
Linker flags might be missing in the build process.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Current Behavior
MeshSync doesn't discover this resource type.

Implementation
Add support for discovering this Kubernetes resource type. Do the same thing that was done here - 1b640b8, but for persistent volumes

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Description
If MeshSync has been deployed with one Meshery Server and that Meshery Server is replace with a new Meshery Server, MeshSync doesn't connect.

Environment:

• Version: v0.5.2

Current Behavior
The golang version and key dependencies need upgraded here.

Resources

Alternatives / Additional Context

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Current Behavior
This repo was just created and needs a description of the project.

Desired Behavior
The GitHub Action workflows need revision.

Revise CI workflows to build MeshSync; have release channels; push to Docker Hub layer5/meshsync.

• ciuser has permission to write to Docker Hub repo
• repo has secret IMAGE_NAME="layer5/meshsync"
• use PAT for Release Drafter

Current #State:
See the white background between the man and woman in the image below that needs to be updated to a better version in the README file.

Desired State:
This is the desired image.

Replace with the image below.

Contributor Resources

• Meshery documentation site
• Meshery documentation source
• Instructions for contributing to documentation

Current Behavior

From #103 - "Error codes are yet to be created for the functionalities that has been introduced in this PR, which would be addressed in a different PR."

Desired Behavior
Robustly written error codes

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Using meshery/meshery workflows as examples, incorporate additional golang build checks into the ci.yml in this repo.

Originally posted by @leecalcote in #93 (comment)

Current Behavior
MeshSync doesn't discover this resource type.

Implementation
Add support for discovering this Kubernetes resource type. Do the same thing that was done here - 1b640b8, but for persistentvolumeclaims

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Current State:
This repo was just created and needs a description of the project.

Desired State:
The MeshSync logo and a short blurb about MeshSync should be added to this repo.

Contributor Resources

• Logo - meshsync.svg.zip

Current Behavior

Desired Behavior

Meshsync needs the helm chart

• It needs to include in the Meshery helm chart.

Resources

Alternatives / Additional Context

Description
https://github.com/meshery/meshsync/runs/5869121512?check_suite_focus=true#step:5:114

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Current State:

https://github.com/layer5io/meshsync#layer5-repo-template

Desired State:

Nowadays, we are going to release a new version meshSync and we can add the contents here.

Contributor Resources

• Meshery documentation site
• Meshery documentation source
• Instructions for contributing to documentation

Description

Current Behavior
Meshsync should be acting as an admission controller, listening to new CRs and web hooks created. Currently it does discovery for only the existing CRs which exist in the cluster during boot up of the MeshSync controller.

Desired Behavior
New CRs that get added to the cluster should be discovered by MeshSync.

Resources

Alternatives / Additional Context

Description

Installed and deleted Istio from Meshery UI but the Meshery Dashboard still shows one pod from istio-system namespace even though it is terminated.

Expected Behavior

The dashboard should show no resources if they are not present in the cluster.

Environment:

• OS: Ubuntu
• Browser: Brave (Chromium)
• Meshery Version: edge-latest (v0.5.66)

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Current State:

No meshery logo in readme.

Desired State:

Add a meshery logo by taking reference from github.com/meshery/meshery and make it match suitably in dark and light mode.

Contributor Resources

• Meshery documentation site
• Meshery documentation source
• Instructions for contributing to documentation

Current Behavior
MeshSync doesn't discover endpoints resource type.

Desired Behavior
Add support for discovering endpoints Kubernetes resource type. Do the same thing that was done here - 1b640b8, but for STatefulSet

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Current Behavior
Support reinitialization of MeshSync and Meshery Server connections.

Situation
Meshery Server connects to MeshSync, synchronizes, then becomes disconnected.

Scenarios
Support the following two situations:

1. Reconnect prior Meshery Server instance to existing MeshSync instance.
2. Connect new Meshery Server to existing MeshSync instance.

Document the build, run and test instructions for MeshSync.

Include the enhancement to use this standard Makefile includes that we have in each of the other repos for an improved make command DevEx?

Originally posted by @leecalcote in #216 (comment)

Contributor Resources

• Meshery documentation site
• Meshery documentation source
• Instructions for contributing to documentation

Copy workflows:

• https://github.com/layer5io/meshery/blob/master/.github/release-drafter.yml
• https://github.com/layer5io/meshery/blob/master/.github/workflows/release-drafter.yml

Current Behavior
Currently the slack.yml is outdated. Also there is no automated way of notifying the slack channel when a "good first issue" has been created.

Desired Behavior
Update slack.yml and add newcomer-alert.yml to the Github workflow.

Resources
Add the updated slack.yml file and the newcomer-alert.yml file to the .github/workflow folder.

Files needed:
https://github.com/meshery/meshery-istio/blob/master/.github/workflows/slack.yml
https://github.com/layer5io/layer5/blob/master/.github/workflows/newcomers-alert.yml

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 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

Resources
Refer to the Contributing guide

Environment:

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

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

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
Related to issue #86, new MeshSync release numbers are not showing in the Meshery UI. Is this a MeshSync issue?

Linker flags might be missing in the build process.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

See meshery/meshery-operator#84

Description
Fix minikube/KIND cluster specific container issues.

• Roles/Cluster roles need changes

Screenshots

Environment:

• 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

Current Behavior

Desired Behavior

Resources

Alternatives / Additional Context

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Description

Expected Behavior

Screenshots

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

move to meshery.meshsync.k8s?

Originally posted by @leecalcote in #120 (comment)

Description

Currently, we are using the Logo of Layer5 instead of Meshery. This repository is under the organization Meshery, so, there should be an image of Meshery.

How to resolve this

• Go to .github and replace this welcome image with the new one:

• Make sure to display the images conditionally, based on the theme selected by user.
  Here's the sample code:

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/GiorgosXou/Random-stuff/main/Programming/StackOverflow/Answers/70200610_11465149/w.png">
  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/GiorgosXou/Random-stuff/main/Programming/StackOverflow/Answers/70200610_11465149/b.png">
  <img alt="Meshery Logo" src="">
</picture>

New images are:

• Download these images, and upload with an appropriate name. Make sure to use conditional rendering as described above.

• After uploading the image, and removing the previous image, go to .github/config.yml folder and update the reference to previous image to the new image in the following part:

firstPRMergeComment: >
  Thanks for your contribution to the Layer5 and Meshery community! :tada:
   
  ![Congrats!](https://raw.githubusercontent.com/meshery/meshery.io/master/.github/welcome/Layer5-celebration.png)
    	   	    	    	 :star: Please leave a [star on the project](../stargazers). :smile:

Here, replace ![Congrats!](https://raw.githubusercontent.com/meshery/meshery.io/master/.github/welcome/Layer5-celebration.png) with the code

<picture>
  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/GiorgosXou/Random-stuff/main/Programming/StackOverflow/Answers/70200610_11465149/w.png">
  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/GiorgosXou/Random-stuff/main/Programming/StackOverflow/Answers/70200610_11465149/b.png">
  <img alt="Shows a black logo in light color mode and a white one in dark color mode." src="https://user-images.githubusercontent.com/25423296/163456779-a8556205-d0a5-45e2-ac17-42d089e3c3f8.png">
</picture>

make sure to change the image sources with the path to image in the folder where you upload it.

• That's it.

Environment:

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

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Current Behavior
Currently, MeshSync workflows only include lint checks.

Desired Behavior
MeshSync workflows are in need of having the full gamut of checks configured.

// @Aisuko, @ramrodo, @shubhank-saxena

Desired Behavior
Use the same discuss shield from meshery/meshery's readme.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Description:

This repository should have the label commenter workflow.
It would run whenever an issue/pr is labelled with one of the targeted labels and comment down any relevant information.

Contributor Reference:

The workflow would use: https://github.com/peaceiris/actions-label-commenter

A sample workflow is defined in: https://github.com/meshery/meshery/blob/master/.github/workflows/label-commenter.yml.

It would also need a sample configuration which is defined in: https://github.com/meshery/meshery/blob/master/.github/label-commenter-config.yml

NOTE:

• In the above configuration https://github.com/meshery/meshery/blob/88d1c7c559259775ce2affab2a15a32c673c3f52/.github/label-commenter-config.yml#L26-L41 are specific to Meshery and won't be needed on every repository.
• Do comment in PR if you find any label is missing for the repo.

Current Behavior
Repo is empty.

Desired Behavior
Initialize repo with MeshSync's custom controller

Current Behavior

MeshSync performs discovery of specific Kubernetes API types using watches and sharedInformers.

Desired Behavior

Enhance MeshSync to use Streaming Lists when available in the managed Kubernetes cluster.

Implementation:

1. Verify whether Streaming Lists are available. If so, use them.

Acceptance Criteria

1. When Streaming Lists are not available, downgrade to current methodology.
2. Confirm that all of the same resource details are retrieved via Streaming Lists as are retrieved using the current methodology.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Current Behavior
MeshSync doesn't discover this resource type.

Implementation
Add support for discovering this Kubernetes resource type. Do the same thing that was done here - 1b640b8, but for ingresses

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in Figma (open invite).
• Fill-in a Community Member Form and join the Community Slack for access.

Desired Behavior

Meshery users, particularly those running Docker Desktop can benefit from multi-platform images of Meshery Server.

Implementation

Refactor existing stable and edge build and release workflows to use docker-build-push actions. See https://github.com/meshery/meshery/blob/master/.github/workflows/build-and-release-dde.yml as an example.

Be aware of local binaries and their needs:

1. layer5/kubeopenapi-json

Acceptance Tests

1. platform: linux/amd64,linux/arm64 should both be supported.2.

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Current Behavior

Repo needs dependabot.yml added.

Implementation

Copy from meshery/meshery as a base template.

Reference:

• Meshery Build & Release Strategy

Description
MeshSync publishing-to: http://localhost:4222 - https://github.com/layer5io/meshsync/blob/f133108ddd96c9a053fbbd10b710002c4cd4aa35/internal/config/config.go#L48

Expected Behavior
Should be publishing to the named broker service using kubernetes svc naming.

Current Behavior
MeshSync is sending uninteresting updates to Meshery Server as part of its synchronization routine.

Desired Behavior
Incorporate additional intelligence to only send materially interesting updates.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Description
Whenever meshsync runs or someone import it, it init internal/cache package.
To init a package an init() function is called.
There is no error handling in that package

Expected Behavior
There should be error handling in the init() function.

Current Behavior

The project's current issue templates are missing an open invitation link where new contributors can join the community's Figma team and view user interface designs and other UX projects.

Desired Behavior

Each template that has a reference to Figma in its resources section should an invite link added.

Implementation

In each issue template that refers to Figma, replace the current line referring to Figma with this line:

- 🎨 Wireframes and [designs for Meshery UI](https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/qJy1c95qirjgWQODApilR9)```

Acceptance Tests

1. All references to Figma include the "open invite" link.

Contributor Resources

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.