Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Publish multiple version of k8s in the e2e tests. #482

Open
asubedy opened this issue Sep 8, 2022 · 9 comments
Open

[CI] Publish multiple version of k8s in the e2e tests. #482

asubedy opened this issue Sep 8, 2022 · 9 comments
Labels
area/ci Continuous integration | Build and release issue/remind Issue progress check issue/willfix This issue will be fixed

Comments

@asubedy
Copy link
Member

asubedy commented Sep 8, 2022

Current Behavior

Currently, during the e2e tests, although we are running tests using 3 version of Kubernetes, but while updating the docs we only publish one version of tests.

Desired Behavior

We need to publish all the k8s version to the docs.

Implementation

Change this to array or list of k8s version instead of single version.

Acceptance Tests


Contributor Guides and Resources

@asubedy asubedy added the area/ci Continuous integration | Build and release label Sep 8, 2022
@welcome
Copy link

welcome bot commented Sep 8, 2022

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack.

@stale
Copy link

stale bot commented Oct 14, 2022

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.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Oct 14, 2022
@stale
Copy link

stale bot commented Oct 23, 2022

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Oct 23, 2022
@deepeshaburse deepeshaburse added issue/remind Issue progress check and removed issue/stale Issue has not had any activity for an extended period of time labels Oct 24, 2022
@github-actions
Copy link

Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.


        Be sure to join the community, if you haven't yet and please leave a ⭐ star on the project 😄 on the project.

@github-actions github-actions bot reopened this Oct 24, 2022
@stale
Copy link

stale bot commented Nov 29, 2022

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.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Nov 29, 2022
@leecalcote leecalcote added the issue/willfix This issue will be fixed label Nov 30, 2022
@stale stale bot removed the issue/stale Issue has not had any activity for an extended period of time label Nov 30, 2022
@AugustasV AugustasV self-assigned this Feb 8, 2023
@VaibhavMalik4187
Copy link

@leecalcote can I work on this?

@leecalcote
Copy link
Member

@AugustasV @Revolyssup @asubedy has this been completed?

@asubedy
Copy link
Member Author

asubedy commented Aug 14, 2023

No I don't think this is completed, although we do publish test on multiple version of k8s but each test creates a new entries. They are not clubbed together. I guess this was something required when I was told to opened the issue.

@saurabh100ni
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Continuous integration | Build and release issue/remind Issue progress check issue/willfix This issue will be fixed
Projects
None yet
Development

No branches or pull requests

7 participants