pkg syscall (freebsd-arm64), const DLT_RAW ideal-int
pkg syscall (freebsd-arm64), const DLT_RIO = 124
pkg syscall (freebsd-arm64), const DLT_RIO ideal-int
pkg syscall (freebsd-arm64), const DLT_SCCP = 142
pkg syscall (freebsd-arm64), const DLT_SCCP ideal-int
pkg syscall (freebsd-arm64), const DLT_SITA = 196
pkg syscall (freebsd-arm64), const DLT_SITA ideal-int
pkg syscall (freebsd-arm64), const DLT_SLIP = 8

## Changelog since v1.7.4

### Other notable changes

* Bumped Heapster version to 1.4.2 - more details https://github.com/kubernetes/heapster/releases/tag/v1.4.2. ([#51620](https://github.com/kubernetes/kubernetes/pull/51620), [@piosz](https://github.com/piosz))

pkg syscall (darwin-arm64), const SYS_GETGID ideal-int
pkg syscall (darwin-arm64), const SYS_GETGROUPS = 79
pkg syscall (darwin-arm64), const SYS_GETGROUPS ideal-int
pkg syscall (darwin-arm64), const SYS_GETHOSTUUID = 142
pkg syscall (darwin-arm64), const SYS_GETHOSTUUID ideal-int
pkg syscall (darwin-arm64), const SYS_GETITIMER = 86
pkg syscall (darwin-arm64), const SYS_GETITIMER ideal-int
pkg syscall (darwin-arm64), const SYS_GETLCID = 395

<pre>
var a [10]int
s1 := a[3:7]   // underlying array of s1 is array a; &amp;s1[2] == &amp;a[5]
s2 := s1[1:4]  // underlying array of s2 is underlying array of s1 which is array a; &amp;s2[1] == &amp;a[5]
s2[1] = 42     // s2[1] == s1[2] == a[5] == 42; they all refer to the same underlying array element

var s []int
s3 := s[:0]    // s3 == nil
</pre>


<h4>Full slice expressions</h4>

<p>

first point, but up to now pod scheduling was still done without considering that the remaining storage capacity may not be enough to start a new pod. [Storage capacity tracking](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking), a new alpha feature, addresses that by adding an API for a CSI driver to report storage capacity and uses that information in the Kubernetes scheduler when choosing a node for a pod. This feature serves as a stepping stone...

### Storage Capacity and Volume Expansion Are Generally Available

[Storage capacity tracking](https://github.com/kubernetes/enhancements/issues/1472)
supports exposing currently available storage capacity via [CSIStorageCapacity objects](https://kubernetes.io/docs/concepts/storage/storage-capacity/#api)
and enhances scheduling of pods that use CSI volumes with late binding.