Release/2022.06.1 - NOT TO BE MERGED #11411
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A [regression by Replicated](replicated-collab/replicated-gitpod#27) introduced a breaking change to how to deploy KOTS releases that included a Helm chart between v1.72.0 and v1.72.2. The [change](replicatedhq/kots@77690e5) only affects manifests that use native Helm but the legacy implementation inside KOTS.
…pshot CRD exists Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>
An errant `git rebase` accidentally merged in the customer ID into telemetry data, bypassing a later check in telemetry collection that checked the `sendCustomerID` field. This commit restores the appropriate check.
This PR updates the new preview installation method, to be called `local-preview`. This is part of the recent change across the documentation https://github.com/gitpod-io/website/pull/2326 The image tag is still `preview-install` in the readme's and other documentations, but it will be updated once we start publishing releases with it. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
Fixes #10766 This PR adds a new `experimental.telemetry.data.platform` config option that is then passed to `GITPOD_INSTALLATION_PLATFORM` env variable, which is then transmitted by the `gitpod-telemetry` job as the `platform` property into our telemetry store. The value of this env variable is then overrided by each install method. This env can have the following values: - `installer` by default as when the installation is done directly through the installer, We don't have enough information about the environment. - [One of the `distribution` values](https://docs.replicated.com/reference/template-functions-static-context#distribution) when done through `kots`. This would have the distribution in which Gitpod is being installed, and is dependent on `kots`. - `local-preview` when the installation is done through the new preview install method. As the changes show in the PR, each installation method overrides the value. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
Currently, It takes a while before Gitpod is ready even though the status says `Gitpod is running` as its not checking for readyness. This PR updates the output to separate btw `starting` and `running`. `Gitpod is running` message is showed only when we see that the `gitpod-telemetry-init` job has run which happens when all pods are ready. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
Due to the way docker works in non-native platforms, It is very hard to have a consistent experience across all platforms as we can't just use the [docker bridge netwrok IP's in non-native platforms](https://docs.docker.com/desktop/networking/). This means that users have to search their Host IP, and use It to get up and working [which we tried, but understand that it's not a good UX](https://github.com/gitpod-io/website/pull/2349). But users can use `127-0-0-1.nip.io` as the DOMAIN which resolves to `127.0.0.1` and is available in all platforms as its `localhost`. This works well and good for all user communication but internal communication fails as `127-0-0-1.nip.io` for them is something else. So, This PR fixes that by adding new coredns `gitpod.db` coredns config essentially asking to route all `127-0-0-1.nip.io` to `proxy.default.svc.cluster.local`. [As k3s does not yet support overriding coredns config in a sane-way](k3s-io/k3s#462) ,We instead skip the default coredns by adding `coredns.yaml.skip` file, and adding our own `custom-coredns.yaml` which is just plain `coredns.yaml` that comes with `k3s`, added with gitpod config. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
This PR updates the `local-preview` to printout the Domain of the Gitpod Instance for users to access. Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
|
@mrsimonemms: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
roboquat
added
do-not-merge/release-note-label-needed
size/XXL
size/XS
and removed
size/XXL
labels
felladrin
force-pushed
the
release/2022.06.1
branch
from
540ed96 to
267953e
Compare
…gin to work when user has proxies
|
/werft run publish-to-kots 👍 started the job as gitpod-build-release-2022.06.1.4 |
This PR updates the `entry-point.sh` to run a parallel step
that waits for the gitpod pods to be ready, and manually executes
the cronjob once its necessary.
This is necessary as our telemetry `cronjobs` are only ran
daily in the midnight, and we can't expect this schedule to work
for local previews as they are short lived.
example data that we get:
```
client.Track(&analytics.Track{
UserId: "334c379a-afee-4882-ba44-fbd7dfc0a8b0",
Event: "Installation telemetry",
Properties: map[string]interface{}{
"customerID": "",
"platform": "local-preview",
"totalInstances": 0,
"totalUsers": 0,
"totalWorkspaces": 0,
"version": "tar-preview-tel-init.4",
},
})
```
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
|
/werft run publish-to-kots 👍 started the job as gitpod-build-release-2022.06.1.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
June hotfix release
PRs
DOMAINin the output #11341127-0-0-1.nip.ioforDOMAIN#11242startingandrunning#11260telemetry.dataconfig option for telemetry #10925preview-installtolocal-preview#11037[ws-manager] do not overwrite failed state #11419Excluding due to being reverted in Revert "[ws-manager] do not overwrite failed state" #11427Related Issue(s)
Fixes #
How to test
Release Notes
Documentation
Werft options: