service-mesh-labs
service-mesh-labs copied to clipboard
updated instructions and image of adapters
Signed-off-by: asubedy [email protected]
Description Updated Instructions and images of adapters
This PR fixes #51
Notes for Reviewers The PR is not completed yet, as of now Linkerd and NSM are updated. I will be updating the same after each adapter instructions are updated
Signed commits
- [X] Yes, I signed my commits.
NOTE: If you see a vim page please press
q
andy
. Also if you see an error statingFailed to open Meshery in browser, please point your browser to....
please ignore it. To know that the Meshery has loaded with all the components connected, runmesheryctl system status
{{execute}}. If all the components are in ready state you can open Mehsery UI tab with everything connected.
@leecalcote I am thinking of putting the above note(in this way itself) after the install command for this issue I can not figure out any specific solution to avoid the vim mode. This small note can help people to continue with the instructions.
The last commit dealt with these changes:
- Bumped Kubernetes version from 1.18 to 1.22
- Updated instructions and Screenshots of Kuma adapter
- Added a small note to help users to navigate on the katacoda terminal after the installation command
- some minor screenshot updates on other adapters
@asubedy don't worry about DCO here. We'll get you covered.
@Revolyssup, please track down the issue with OSM in the Meshery Adapter for OSM.
@asubedy will you open an issue with adapter logs on meshery/meshery-osm
repo?
@asubedy will you open an issue with adapter logs on
meshery/meshery-osm
repo?
How do I see the adapter logs? From the katacoda scenario or from my local machine?
@Revolyssup, please track down the issue with OSM in the Meshery Adapter for OSM.
What's the issue with OSM adapter?
@Revolyssup, please track down the issue with OSM in the Meshery Adapter for OSM.
What's the issue with OSM adapter?
When trying to install OSM Servive mesh we get an error, that says we require Kubernetes version greater than or equal to 1.19. This is because on the lab we are using the pre runnung cluster version of 1.18. And there are no image of other version of kubernetes mentioned on the katacoda docs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go.