Remove obsolete note regarding Alpine DNS issues

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

What does this MR do?

Remove obsolete note regarding Alpine DNS issues

Related issues

#4129 (closed) was resolved long ago.

The root cause was https://gitlab.alpinelinux.org/alpine/tsc/-/issues/43#note_306270 which was resolved with the release of Alpine 3.18.

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.

Thanks for your contribution to GitLab @candrews!

Did you know about our community forks? Working from there will make your contribution process easier. Please check it out!

• If you need help, page a coach by clicking here or come say hi on Discord.
• When you're ready, request a review by clicking here.
• We welcome AI-generated contributions and offer complimentary access to GitLab Duo!

Some contributions require several iterations of review and we try to mentor contributors during this process. However, we understand that some reviews can be very time consuming. If you would prefer for us to continue the work you've submitted now or at any point in the future please let us know.

If you're okay with being part of our review process (and we hope you are!), there are several initial checks we ask you to make:

• The merge request description clearly explains:
  • The problem being solved.
  • The best way a reviewer can test your changes (is it possible to provide an example?).
• If the pipeline failed, do you need help identifying what failed?
• Check that Go code follows our Go guidelines.
• Read our contributing to GitLab Runner document.

This message was generated automatically. Improve it or delete it.

added 1st contribution Community contribution workflowin dev labels

assigned to @candrews

changed the description

This merge request will be counted as part of the running Hackathon!

Find yourself in the Hackathon Leaderboard or check out the Hackathon page for more information!

This message was generated automatically. Improve it or delete it.

added Hackathon label

added linked-issue label

@gitlab-bot ready

Posted via contributors.gitlab.com.

added workflowready for review label and removed workflowin dev label

Hi @axil! Please review this documentation merge request. This message was generated automatically. Improve it or delete it.

added documentation twtriaged labels

requested review from @axil

@axil, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
• If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
• Please ensure the group's Product Manager has validated the linked issue.

This message was generated automatically. Improve it or delete it.

added docs-only label

added Category:Runner Core devopsverify grouprunner labels

mentioned in issue gitlab-org/quality/triage-reports#22003 (closed)

approved this merge request

Hi @axil ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. Improve it or delete it.

added Technical Writing label

started a merge train

Thanks!

changed milestone to %17.9

added sectionci label

added docsimprovement label

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@dbickford (UTC-7)	@ajwalker (UTC+0)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

merged

mentioned in commit 177b6638

added typemaintenance label

@candrews, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Request access to our community forks to receive complimentary access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.

Thanks for your help!

This message was generated automatically. Improve it or delete it.

mentioned in merge request jointeg/infrastructure/compose-services!144