-
Notifications
You must be signed in to change notification settings - Fork 244
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
Remove podman from experimental mode #6628
Remove podman from experimental mode #6628
Conversation
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
aa4164c
to
28695f9
Compare
28695f9
to
5f12466
Compare
2621fdf
to
613b2c7
Compare
This PR is ready for review. I would like to work on the latest task (add documentation explaining the limitations of podman implementations) on a different PR. |
d3c0d8a
to
b8e1946
Compare
@@ -146,9 +146,8 @@ If you skipped Step 0 and selected "starter project", your output will be slight | |||
### Step 2. Enabling the experimental mode |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove this section entirely now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer not to, by changing only the strict minimum the blog posts (here, we need to remove the links to the removed experimental-mode page, to make the website build)
@@ -28,8 +28,6 @@ Similarly to how `odo dev` requires specifying the target platform (using the `- | |||
ODO_EXPERIMENTAL_MODE=t odo logs --platform podman | |||
``` | |||
|
|||
As a reminder, Podman support in `odo` is still [experimental](../docs/user-guides/advanced/experimental-mode) and requires you to [opt in](../docs/user-guides/advanced/experimental-mode#enabling-the-experimental-mode) if you want to try it out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would keep this as is since at the time of v3.7.0 podman was still in experimental mode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm reverting it, and only removing links
@@ -2,7 +2,7 @@ | |||
title: odo describe component | |||
--- | |||
|
|||
`odo describe component` command is useful for getting information about a component managed by `odo`. | |||
`odo describe component` command is useful for getting information about a component. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still true, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it isn't anymore since #6615
@@ -190,7 +190,6 @@ Options here are mostly used for debugging and testing `odo` behavior. | |||
| `DEVFILE_PROXY` | Integration tests will use this address as Devfile registry instead of `registry.stage.devfile.io` | v3.0.0-beta3 | `my-registry.example.com` | | |||
| `TELEMETRY_CALLER` | Caller identifier passed to [telemetry](https://github.com/redhat-developer/odo/blob/main/USAGE_DATA.md). Case-insensitive. Acceptable values: `vscode`, `intellij`, `jboss`. | v3.1.0 | `intellij` | | |||
| `ODO_TRACKING_CONSENT` | Useful for controlling [telemetry](https://github.com/redhat-developer/odo/blob/main/USAGE_DATA.md). Acceptable values: `yes` ([enables telemetry](https://github.com/redhat-developer/odo/blob/main/USAGE_DATA.md) and skips consent prompt), `no` (disables telemetry and consent prompt). Takes precedence over the [`ConsentTelemetry`](#preference-key-table) preference. | v3.2.0 | `yes` | | |||
| `ODO_EXPERIMENTAL_MODE` | Whether to enable experimental features. See [Experimental Mode](../user-guides/advanced/experimental-mode) for more details. Acceptable values: boolean values<sup>(1)</sup> | v3.3.0 | `true` | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you comment this instead of completely removing it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I notice that this makes the build fail, even when the link is into a comment (https://app.netlify.com/sites/odo-docusaurus-preview/deploys/6405b74c3f18100008d06cfd):
- On source page path = /docs/overview/configure:
-> linking to ../user-guides/advanced/experimental-mode (resolved as: /docs/user-guides/advanced/experimental-mode)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be because you renamed the experimental-mode.md file. I would remove the link like you've done at other places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm reverting to remove completely the line. The commit is accessible if we want to revert the deletion
/hold cancel |
@@ -50,7 +50,6 @@ Example: | |||
#### Using `odo` with Podman | |||
|
|||
Based on your valuable feedback, we have worked on improving the experience of using `odo` with Podman. | |||
Note that this is still [experimental](../docs/user-guides/advanced/experimental-mode) and requires you to [opt in](../docs/user-guides/advanced/experimental-mode#enabling-the-experimental-mode) if you want to try it out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it's fine to keep this as it is (by removing link to the experimental mode doc) since at the time of v3.4.0 Podman was still in the experimental mode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm reverting it, and only removing links
b8e1946
to
90342a4
Compare
Co-authored-by: Armel Soro <armel@rm3l.org>
90342a4
to
536bedc
Compare
Broken links: |
See #6628 (comment) |
536bedc
to
6fe424a
Compare
6fe424a
to
b1ebb98
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/override windows-integration-test/Windows-test |
@feloy: Overrode contexts on behalf of feloy: windows-integration-test/Windows-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
* Remove podman from experimental mode * Remove env var for odo dev * Cleanup tests and sources about experimental mode * Hide "Experimental mode" doc page * Cleanup latest commit * doc odo dev --platform podman * Doc other commands * Apply suggestions from code review Co-authored-by: Armel Soro <armel@rm3l.org> * Remove more ODO_EXPERIMENTAL_MODE from latest commits on main * Remove reference to Experimental mode from blog posts --------- Co-authored-by: Armel Soro <armel@rm3l.org>
What type of PR is this:
/kind feature
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6592
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: