- Fixed an issue in register-gen where imports for k8s.io/apimachinery/pkg/runtime and k8s.io/apimachinery/pkg/runtime/schema were missing. ([#130392](https://github.com/kubernetes/kubernetes/pull/130392), [@mrIncompetent](https://github.com/mrIncompetent)) [SIG API Machinery]

- Fixed incorrect "v1 Binding is deprecated in v1.6+" warning in kube-scheduler log. ([#125540](https://github.com/kubernetes/kubernetes/pull/125540), [@pohly](https://github.com/pohly)) [SIG API Machinery]
- Fixed the comment for the Job's managedBy field. ([#124793](https://github.com/kubernetes/kubernetes/pull/124793), [@mimowo](https://github.com/mimowo)) [SIG API Machinery and Apps]

- Added a detailed event for in-place pod vertical scaling completed, improving cluster management and debugging. ([#130387](https://github.com/kubernetes/kubernetes/pull/130387), [@shiya0705](https://github.com/shiya0705)) [SIG API Machinery, Apps, Autoscaling, Node, Scheduling and Testing]

- The v1 Endpoints API is now officially deprecated (though still fully supported). The API will not be removed, but all users should use the EndpointSlice API instead. ([#130098](https://github.com/kubernetes/kubernetes/pull/130098), [@danwinship](https://github.com/danwinship)) [SIG API Machinery and Network]

### API Change

- Restore --verify-only function in code generation wrappers. ([#123261](https://github.com/kubernetes/kubernetes/pull/123261), [@skitt](https://github.com/skitt)) [SIG API Machinery]
- Sample-apiserver manifest example will have correct RBAC ([#123479](https://github.com/kubernetes/kubernetes/pull/123479), [@Jefftree](https://github.com/Jefftree)) [SIG API Machinery and Testing]

        byte[] customData = new byte[8];
        customData[0] = 0x01;
        customData[1] = 0x02;

        byte[] machineId = new byte[32];
        machineId[0] = 0x10;
        machineId[1] = 0x11;
        machineId[2] = 0x12;

        AvSingleHost avSingleHost = new AvSingleHost(customData, machineId);

        assertNotNull(avSingleHost);
        byte[] value = avSingleHost.getRaw();
        assertNotNull(value);

        this(encode(customData, machineId));
    }

    private static byte[] encode(final byte[] customData, final byte[] machineId) {
        final int size = 8 + 8 + 32;
        final byte[] enc = new byte[size];
        SMBUtil.writeInt4(size, enc, 0);
        SMBUtil.writeInt4(0, enc, 4);
        System.arraycopy(customData, 0, enc, 8, 8);
        System.arraycopy(machineId, 0, enc, 16, 32);

    /**
     * A Hybrid node tries to resolve a name using the nameserver first. If
     * that fails use the broadcast address. This is the default if a nameserver
     * is provided. This is the behavior of Microsoft Windows machines.
     */

    public static final int H_NODE = 3;

    /**
     * Unknown MAC Address
     */

        NetbiosAddress mockHost = mock(NetbiosAddress.class);
        SecureRandom mockRandom = mock(SecureRandom.class);

        // Create a machine ID (32 bytes)
        byte[] machineId = new byte[32];
        mockRandom.nextBytes(machineId);

        lenient().when(mockConfig.getDefaultDomain()).thenReturn("TESTDOMAIN");
        lenient().when(mockConfig.isUseUnicode()).thenReturn(true);

Linux containers run using the same Linux kernel of the host (machine, virtual machine, cloud server, etc). This just means that they are very lightweight (compared to full virtual machines emulating an entire operating system).

This way, containers consume **little resources**, an amount comparable to running the processes directly (a virtual machine would consume much more).