[前チャプターのHTTPSについて](https.md){.internal-link target=_blank}では、HTTPSがどのようにAPIを暗号化するのかについて学びました。

通常、アプリケーションサーバにとって**外部の**コンポーネントである**TLS Termination Proxy**によって提供されることが一般的です。このプロキシは通信の暗号化を担当します。

さらにセキュアな通信において、HTTPS証明書の定期的な更新を行いますが、これはTLS Termination Proxyと同じコンポーネントが担当することもあれば、別のコンポーネントが担当することもあります。

### HTTPS 用ツールの例
TLS Termination Proxyとして使用できるツールには以下のようなものがあります：

* Traefik
    * 証明書の更新を自動的に処理 ✨
* Caddy
    * 証明書の更新を自動的に処理 ✨
* Nginx

     * ScheduledExecutorService#scheduleWithFixedDelay} method.
     *
     * @param initialDelay the time to delay first execution
     * @param delay the delay between the termination of one execution and the commencement of the
     *     next
     * @since 33.4.0 (but since 28.0 in the JRE flavor)
     */
    @IgnoreJRERequirement // Users will use this only if they're already using Duration

            byte[] buffer = new byte[100];
            // Create "Test\0" in UTF-16LE with proper null terminator
            byte[] testBytes = Strings.getUNIBytes("Test");
            System.arraycopy(testBytes, 0, buffer, 0, 8);
            buffer[8] = 0; // null terminator low byte
            buffer[9] = 0; // null terminator high byte

            String result = testBlock.readString(buffer, 0, buffer.length, 8, true);

where to find the applicable terms.

  Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.

  8. Termination.

  You may not propagate or modify a covered work except as expressly
provided under this License.  Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under

  a user to request FallbackToLogsOnError, which will read from the container's
  logs to populate the termination message if the user does not write to the
  termination message log file. The termination message file is now properly
  readable for end users and has a maximum size (4k bytes) to prevent abuse.
  Each pod may have up to 12k bytes of termination messages before the contents
  of each will be truncated.

    protected long documentSize;

    /** Maximum number of indexer errors allowed */
    protected int maxIndexerErrorCount = 0;

    /** Maximum number of general errors allowed before termination */
    protected int maxErrorCount = 2;

    /** List of finished crawler session IDs for cleanup */
    protected List<String> finishedSessionIdList = new ArrayList<>();

  the iptables or ipvs mode of kube-proxy with `EndpointSlices` enabled. Specifically, if a
  connection for such a service arrives on a node when there are no "Ready" endpoints
  for the service, but there is at least one Terminating pod for that service on the node,
  then kube-proxy will send the traffic to the Terminating pod rather than dropping it. This

* Fix race condition introduced by graceful termination which can lead to a deadlock in kube-proxy ([#72361](https://github.com/kubernetes/kubernetes/pull/72361), [@lbernail](https://github.com/lbernail))
* Support graceful termination with IPVS when deleting a service ([#71895](https://github.com/kubernetes/kubernetes/pull/71895), [@lbernail](https://github.com/lbernail))

        int len = 0;
        while (src[srcIndex + len] != (byte) 0x00) {
            if (len++ > max) {
                throw new RuntimeCIFSException("zero termination not found: " + this);
            }
        }
        return len;
    }

    @Override
    public int encode(final byte[] dst, int dstIndex) {

* kube-proxy in IPVS mode will stop initiating connections to terminating pods for services with sessionAffinity set. ([#71834](https://github.com/kubernetes/kubernetes/pull/71834), [@lbernail](https://github.com/lbernail))
* kubeadm: improve hostport parsing error messages ([#71258](https://github.com/kubernetes/kubernetes/pull/71258), [@bart0sh](https://github.com/bart0sh))