Skip to content

docs: update insecure HTTP links to HTTPS in comments and docs #16552

@Ankitsinghsisodya

Description

@Ankitsinghsisodya

Summary

Several source code comments, CRD YAML descriptions, configmap comments, and generated API docs contain insecure http:// links that should be upgraded to https://.

Affected files

  • pkg/apis/serving/v1/revision_types.go — bit.ly ref links in ContainerStatuses and InitContainerStatuses comments
  • pkg/autoscaler/aggregation/max/window.go — Wayback Machine link in ascending minima algorithm comment
  • config/core/300-resources/revision.yaml — bit.ly ref links in containerStatuses and initContainerStatuses field descriptions
  • config/core/configmaps/autoscaler.yaml — bit.ly link in activator-capacity algorithm comment
  • docs/serving-api.md — bit.ly href links in generated API reference for RevisionStatus fields
  • DEVELOPMENT.md — Google Cloud Console link

Expected behavior

All reference links in documentation and comments should use https:// to avoid insecure HTTP connections.

/kind cleanup

Metadata

Metadata

Labels

kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions