MOVD	$499, R12
	B	runtime·callbackasm1(SB)
	MOVD	$500, R12
	B	runtime·callbackasm1(SB)
	MOVD	$501, R12
	B	runtime·callbackasm1(SB)
	MOVD	$502, R12
	B	runtime·callbackasm1(SB)
	MOVD	$503, R12
	B	runtime·callbackasm1(SB)
	MOVD	$504, R12
	B	runtime·callbackasm1(SB)
	MOVD	$505, R12
	B	runtime·callbackasm1(SB)
	MOVD	$506, R12
	B	runtime·callbackasm1(SB)
	MOVD	$507, R12

	MOVW	$499, R12
	B	runtime·callbackasm1(SB)
	MOVW	$500, R12
	B	runtime·callbackasm1(SB)
	MOVW	$501, R12
	B	runtime·callbackasm1(SB)
	MOVW	$502, R12
	B	runtime·callbackasm1(SB)
	MOVW	$503, R12
	B	runtime·callbackasm1(SB)
	MOVW	$504, R12
	B	runtime·callbackasm1(SB)
	MOVW	$505, R12
	B	runtime·callbackasm1(SB)
	MOVW	$506, R12
	B	runtime·callbackasm1(SB)
	MOVW	$507, R12

				objInfo.TargetReplicationStatus(tgt.ARN) == replication.Failed ||
				ri.OpType == replication.ExistingObjectReplicationType {
				// if metadata is not updated for some reason after replication, such as
				// 503 encountered while updating metadata - make sure to set ReplicationStatus
				// as Completed.
				//
				// Note: Replication Stats would have been updated despite metadata update failure.

// TimeoutHandler returns a [Handler] that runs h with the given time limit.
//
// The new Handler calls h.ServeHTTP to handle each request, but if a
// call runs for longer than its time limit, the handler responds with
// a 503 Service Unavailable error and the given message in its body.
// (If msg is empty, a suitable default message will be sent.)
// After such a timeout, writes by h to its [ResponseWriter] will return
// [ErrHandlerTimeout].
//

			Attempts: 10,
		}, valid: true},
		{name: "valid http status retryOn", in: &networking.HTTPRetry{
			Attempts:      10,
			PerTryTimeout: &durationpb.Duration{Seconds: 2},
			RetryOn:       "503,connect-failure",
		}, valid: true},
		{name: "invalid attempts", in: &networking.HTTPRetry{
			Attempts:      -1,
			PerTryTimeout: &durationpb.Duration{Seconds: 2},
		}, valid: false},

* kube-apiserver: requests to endpoints handled by unavailable extension API servers (as indicated by an `Available` condition of `false` in the registered APIService) now return `503` errors instead of `404` errors. ([#58070](https://github.com/kubernetes/kubernetes/pull/58070), [@weekface](https://github.com/weekface))

	499:  {region: 0x96, script: 0x5b, flags: 0x0},
	500:  {region: 0x107, script: 0x20, flags: 0x0},
	501:  {region: 0x1, script: 0x5b, flags: 0x0},
	502:  {region: 0x166, script: 0x5b, flags: 0x0},
	503:  {region: 0x166, script: 0x5b, flags: 0x0},
	504:  {region: 0x9e, script: 0x5b, flags: 0x0},
	505:  {region: 0x9f, script: 0x5b, flags: 0x0},
	506:  {region: 0x49, script: 0x17, flags: 0x0},

- Resolves a potential issue with GC and NS controllers which may delete objects after getting a 404 response from the server during its startup. This PR ensures that requests to aggregated APIs will get 503, not 404 while the APIServiceRegistrationController hasn't finished its job. ([#104748](https://github.com/kubernetes/kubernetes/pull/104748), [@p0lyn0mial](https://github.com/p0lyn0mial))

pkg syscall (freebsd-arm64), const SYS_UNDELETE ideal-int
pkg syscall (freebsd-arm64), const SYS_UNLINK = 10
pkg syscall (freebsd-arm64), const SYS_UNLINK ideal-int
pkg syscall (freebsd-arm64), const SYS_UNLINKAT = 503
pkg syscall (freebsd-arm64), const SYS_UNLINKAT ideal-int
pkg syscall (freebsd-arm64), const SYS_UNMOUNT = 22
pkg syscall (freebsd-arm64), const SYS_UNMOUNT ideal-int
pkg syscall (freebsd-arm64), const SYS_UTIMENSAT = 547

pkg net/http, const StatusRequestedRangeNotSatisfiable = 416
pkg net/http, const StatusResetContent = 205
pkg net/http, const StatusSeeOther = 303
pkg net/http, const StatusServiceUnavailable = 503
pkg net/http, const StatusSwitchingProtocols = 101
pkg net/http, const StatusTeapot = 418
pkg net/http, const StatusTemporaryRedirect = 307
pkg net/http, const StatusUnauthorized = 401