# Repository settings
Source: https://docs.infraista.com/en/developer-tools/container-registry/repository-settings



Open a repository and go to its **Settings** tab.

## Visibility [#visibility]

* **Private**: only your team, robot tokens and connected clusters can pull.
* **Public**: anyone on the internet can pull without signing in. Don't bake secrets, API keys or
  licensed software into public images.

## Immutable tags [#immutable-tags]

With **Immutable tags** on, a pushed tag can't be overwritten: a push over an existing tag is undone.
Use a new tag for each build, such as the commit's short SHA.

## Retention rules [#retention-rules]

Retention rules delete old tags automatically. A tag is deleted if any rule matches, and each
repository can have up to 5 rules:

| Rule                                            | What it does                     |
| ----------------------------------------------- | -------------------------------- |
| **Keep only the newest N tags**                 | Deletes older tags beyond N      |
| **Delete untagged images after N days**         | Removes images no tag points to  |
| **Delete tags matching a pattern after N days** | For example `pr-*` after 14 days |

Rules run every night at 03:40 UTC, and the newest tag is always kept. Without rules, every tag is kept
until you delete it.

## Garbage collection [#garbage-collection]

When a tag moves to a new image, the old layers are left with nothing pointing to them. The registry
removes these untagged layers every 7 days. Tagged images are only deleted by retention rules or by you.

## Pull access [#pull-access]

Your team can always pull and push. Under **Pull access**, choose which Kubernetes clusters can pull
this repository too. See
[Use with Pipelines and Kubernetes](/en/developer-tools/container-registry/use-with-pipelines-and-kubernetes#pull-from-kubernetes).

## Delete a repository [#delete-a-repository]

In the **Danger zone**, select **Delete repository** and type the name to confirm. This permanently
deletes every tag and image layer in it. Clusters and jobs pulling these images will fail to pull new
copies. This can't be undone.

## Related [#related]

* [Push and pull images](/en/developer-tools/container-registry/push-and-pull-images)
* [Storage and billing](/en/developer-tools/container-registry/storage-and-billing)