|
| 1 | +--- |
| 2 | +title: Planned Migration for go.opentelemetry.io |
| 3 | +date: 2024-08-27 |
| 4 | +author: '[Mike Dame](https://github.com/damemi) (Google)' |
| 5 | +body_class: otel-with-contributions-from |
| 6 | +issue: 5086 |
| 7 | +sig: Go SIG |
| 8 | +cSpell:ignore: vanityurls Yahn |
| 9 | +--- |
| 10 | + |
| 11 | +With contributions from Tyler Yahn and Austin Parker. |
| 12 | + |
| 13 | +## TL;DR |
| 14 | + |
| 15 | +The app that serves requests to [go.opentelemetry.io] will be migrating to a new |
| 16 | +host on September 5, 2024 at approximately 11:00AM Eastern Time. **There are no |
| 17 | +changes required from you**. We are making this announcement because it is |
| 18 | +possible, but unlikely, that there might be downtime during this transition. |
| 19 | + |
| 20 | +## Details |
| 21 | + |
| 22 | +OpenTelemetry is planning to migrate the application that serves all requests |
| 23 | +for `go.opentelemetry.io` to a new host project on September 5, 2024. On this |
| 24 | +date, the current DNS entries for `go.opentelemetry.io` will be updated to point |
| 25 | +to the new host. |
| 26 | + |
| 27 | +This should be a seamless transition, but there is the possibility of downtime |
| 28 | +during this time. The OpenTelemetry engineers will be actively monitoring the |
| 29 | +transition to minimize the risk. |
| 30 | + |
| 31 | +### Affected resources |
| 32 | + |
| 33 | +In the unlikely event of issues, the scope of these planned changes will affect |
| 34 | +Go package downloads for the following domains: |
| 35 | + |
| 36 | +- `go.opentelemetry.io/auto` |
| 37 | +- `go.opentelemetry.io/build-tools` |
| 38 | +- `go.opentelemetry.io/collector-contrib` |
| 39 | +- `go.opentelemetry.io/collector` |
| 40 | +- `go.opentelemetry.io/contrib` |
| 41 | +- `go.opentelemetry.io/otel` |
| 42 | +- `go.opentelemetry.io/proto` |
| 43 | + |
| 44 | +Note that this includes users of any of the following artifacts: |
| 45 | + |
| 46 | +- OpenTelemetry Go language libraries (including Contrib) |
| 47 | +- OpenTelemetry Go Auto-Instrumentation libraries |
| 48 | +- OpenTelemetry Collector libraries (including Contrib) |
| 49 | +- OpenTelemetry Collector Builder. |
| 50 | + |
| 51 | +## What you need to do |
| 52 | + |
| 53 | +**There is no action required from you.** All imports using |
| 54 | +`go.opentelemetry.io` (and submodule paths, for example |
| 55 | +`go.opentelemetry.io/otel`) will continue to work. There are no plans to change |
| 56 | +this. |
| 57 | + |
| 58 | +## What you might notice |
| 59 | + |
| 60 | +There is the possibility of the [go.opentelemetry.io] domain experiencing |
| 61 | +downtime during this transition. If this happens, you might see projects that |
| 62 | +import `go.opentelemetry.io` modules failing to compile. |
| 63 | + |
| 64 | +This could occur due to several factors, including delays in DNS propagation or |
| 65 | +misconfiguration. We will have multiple maintainers working synchronously during |
| 66 | +this time to minimize any downtime that occurs. |
| 67 | + |
| 68 | +If you experience any issues following this transition, please reach out on |
| 69 | +[Slack #otel-go](https://cloud-native.slack.com/archives/C01NPAXACKT) or |
| 70 | +[create an issue](https://github.com/open-telemetry/opentelemetry-go-vanityurls/issues/new) |
| 71 | +over |
| 72 | +[opentelemetry-go-vanityurls](https://github.com/open-telemetry/opentelemetry-go-vanityurls). |
| 73 | + |
| 74 | +## Why are we making this change? |
| 75 | + |
| 76 | +This transition both helps modernize the application serving requests and |
| 77 | +handles an ownership transfer, ensuring that we are able to continue providing |
| 78 | +OpenTelemetry Go packages in a secure and robust manner. |
| 79 | + |
| 80 | +For more details, see |
| 81 | +[the community GitHub issue proposing this change](https://github.com/open-telemetry/community/issues/2260). |
| 82 | + |
| 83 | +[go.opentelemetry.io]: https://go.opentelemetry.io |
0 commit comments