## Known Issues

- Completed pods lose logs across node upgrade ([#32324](https://github.com/kubernetes/kubernetes/issues/32324))
- Pods are deleted across node upgrade ([#32323](https://github.com/kubernetes/kubernetes/issues/32323))
- Secure master -> node communication ([#11816](https://github.com/kubernetes/kubernetes/issues/11816))
- upgrading master doesn't upgrade kubectl ([#32538](https://github.com/kubernetes/kubernetes/issues/32538))

### **Cluster Lifecycle**
#### kubeadm
* [alpha] Manual [upgrades for kubeadm from v1.6 to v1.7](https://kubernetes.io/docs/tasks/administer-cluster/kubeadm-upgrade-1-7/). Automated upgrades ([kubernetes/features#296](https://github.com/kubernetes/enhancements/issues/296)) are targeted for v1.8.

#### Cloud Provider Support

            public jakarta.servlet.http.Part getPart(String name) {
                return null;
            }

            @Override
            public <T extends jakarta.servlet.http.HttpUpgradeHandler> T upgrade(Class<T> handlerClass) {
                return null;
            }

            @Override
            public Object getAttribute(String name) {
                return null;
            }

labels.user_gidNumber=gidNumber
labels.group_gidNumber=gidNumber
labels.gidNumber=gidNumber
labels.user_homeDirectory=Home Directory
labels.homeDirectory=Home Directory
labels.upgrade_title_configuration=Upgrade
labels.upgrade_data_migration=Data Migration
labels.upgrade_reindex=Re-indexing
labels.upgrade_start_button=Start
labels.replace_aliases=Replace Aliases
labels.reset_dictionaries=Reset Dictionaries

  - Renew certs as part of upgrade.
  - New `kubeadm alpha phase certs renew` command for renewing certificates.
  - Certificates created with kubeadm now have improved uniqueness of Distinguished Name fields.
- HA improvements:
  - `kubeadm join --experimental-control-plane` can now be used to join control plane instances to an existing cluster.

// Only changing meaning of fields requires a version bump.
// bucketMetadataFormat refers to the format.
// bucketMetadataVersion can be used to track a rolling upgrade of a field.
type BucketMetadata struct {
	Name                        string
	Created                     time.Time
	LockEnabled                 bool // legacy not used anymore.
	PolicyConfigJSON            []byte

online.help.name.scheduler=scheduler
# Online help key for crawling info.
online.help.name.crawlinginfo=crawlinginfo
# Online help key for backup.
online.help.name.backup=backup
# Online help key for upgrade.
online.help.name.upgrade=upgrade
# Online help key for search request.
online.help.name.sereq=sereq
# Online help key for access token.
online.help.name.accesstoken=accesstoken
# Online help key for suggest.

///

Asegúrate de que el entorno virtual esté activo (con el comando anterior) y luego ejecuta:

<div class="termy">

```console
$ python -m pip install --upgrade pip

---> 100%
```

</div>

## Añade `.gitignore`

Si estás usando **Git** (deberías), añade un archivo `.gitignore` para excluir todo en tu `.venv` de Git.

/// tip | Consejo

///

Certifique-se de que o ambiente virtual esteja ativo (com o comando acima) e execute:

<div class="termy">

```console
$ python -m pip install --upgrade pip

---> 100%
```

</div>

## Adicionar `.gitignore`

Se você estiver usando **Git** (você deveria), adicione um arquivo `.gitignore` para excluir tudo em seu `.venv` do Git.

///

Đảm bảo rằng môi trường ảo đã được kích hoạt (với lệnh trên) và sau đó chạy:

<div class="termy">

```console
$ python -m pip install --upgrade pip

---> 100%
```

</div>

## Thêm `.gitignore`

Nếu bạn sử dụng **Git** (nên làm), hãy thêm một file `.gitignore` để Git bỏ qua mọi thứ trong `.venv`.

/// tip