Adds logic to ensure that only one schema/access set
is cached for each user. This should improve memory
consumption

Adds tests for:
- Cache clearing functionality
- Very basic schema generation

Adding logic to limit number of cached schemas

Three main changes:
- When a count changes, only send that count. This makes the
count socket significantly more usable
- The count buffer will now send a count right away. This allows
a message to launch wihtout an inital buffered wait period
- The count buffer now sends messages every 5 seconds instead of 1

Adds a validate phase to the CI which runs a linter. Also fixes
linter issues discovered during the initial run

Steve Pipeline, Go Version updates

Remove duplicate import and make aliasing of other apiserver imports
consistent throughout steve.

HandlerFromConfig was not used in steve or rancher.

The header defined in RFC 9110[1] is "Accept", not "Accepts". This
change corrects the route filter. Since this API is not documented and
the header was plainly incorrect, no attempt is made at backwards
compatibility.

[1] https://www.rfc-editor.org/rfc/rfc9110.html#name-accept

Usage of the switchstore store was removed when the clusters resource
was removed in dcea1db.

The use of AddNamespaceConstraint was removed in e35b8304 of
rancher/rancher, so there is no possibility of there being a namespace
constraint in the request context. Remove the unused function and the
unused codepath from the rbac store.

Updated logic used to decide when and what schema events are sent
during a watch.

Cleanup and docs

Updates Schemas watch logic.

Changing view links

Bumps dynamic listener to v0.3.5. Adds a small arg change to
account for this version bump which addresses an issue caused by
the new version

Bump dynamic listener to v0.3.5

Changing count watch to only return changed counts

Filtering and sorting needs to operate on unstructured data. It also
needs to operate after the parallel partitioner, higher in the store
stack. This means that the proxy Store needs to return raw, unstructured
data up to the partitioner. This change moves all conversions from
unstructured Kubernetes types to apiserver objects up from the proxy
store into the partitioner.

Extend the partition store to parse query params as list filters. Filter
keys use dot notation to denote the subfield of an object to filter on.
Example:

GET /v1/secrets?filter=metadata.name=foo

Filters are ANDed together, so an object must match all filters to be
included in the list. Example:

GET /v1/secrets?filter=metadata.name=foo&filter=metadata.namespace=bar

Arrays are searched for matching items. If any item in the array
matches, the item is included in the list. Example:

GET /v1/pods?filter=spec.containers.image=alpine

Extend the partition store to parse the "sort" query parameter as a
sorting condition. Dot notation is used to denote the object field.
Preceding the key with "-" denotes descending (reverse) order.

Example sorting by name:

GET /v1/secrets?sort=metadata.name

Reverse sorting by name:

GET /v1/secrets?sort=-metadata.name

All values are converted to strings and sorted lexicographically.

Add tests for RBAC partitioner

Extend the partition store to parse page and pagesize parameters and
return a subset of list results. The total number of pages is included
in the list response.

Request an initial page:

GET /v1/secrets?pagesize=10

or

GET /v1/secrets?pagesize=10&page=1

Request subsequent pages, or arbitrary pages:

GET /v1/secrets?pagesize=10&page=37

If a page number is out of bounds, an empty list is returned.

Cache filtered, sorted results for fast subsequent page retrieval.

Requests for cached queries need to include the list revision number
along with other queries. If no specific revision is requested, a new
fetch is done in order to get the latest revision. The revision is
included in the list response.

Example first request:

GET /v1/secrets?pagesize=10

Example subsequent page request:

GET /v1/secrets?pagesize=10&page=1&revision=107740

Extend the sorting functionality in the partition store to support
primary and secondary sorting criteria. Sorting parameters are specified
by a single 'sort' query and comma separated. Example:

Sort by name and creation time:

GET /v1/secrets?sort=metadata.name,metadata.creationTimestamp

Reverse sort by name, normal sort by creation time:

GET /v1/secrets?sort=-metadata.name,metadata.creationTimestamp

Normal sort by name, reverse sort by creation time:

GET /v1/secrets?sort=metadata.name,-metadata.creationTimestamp

Add an initial README to explain the basics of the API and the new
parameters.

The default chunk size in the partition was set to 100000. It could be
overridden as a larger or smaller number, but not disabled altogether.
This change adds the ability for users to explicitly opt out of the
limit by specifying a negative number or zero. The default behavior is
the same.

Without this change, the cache is checked if a revision is specified,
but the revision is ignored if the value is not found in the cache. This
is a problem if by chance sequential paginated requests land on separate
pods, because a different version number may be fetched on the sequent
request and cause the caches to be inconsistent with one another. This
change ensures that `revision` is passed as `resourceVersion` to the
Kubernetes request, since `revision` has no meaning to Kubernetes.

Pagination, sorting, filtering

Attempts to pass through warning headers which k8s returns.
Requires an update to rancher/apiserver.

Implmentation of warning headers

Expose WarningBuffer type for external use

Watch events need to have a type defined by
k8s.io/apimachinery/pkg/watch to be properly interpreted. Fixes
a bug where this was not the case

Fixes a bug with resource.error watch events

Increase the timeout slightly to avoid the occasional premature timeout.
Fix error message typo.

Bump apiserver

Prior, table client configs were mistakenly swapped out for regular
client configs. This caused requests using these methods to no
longer return table column data under metadata.fields. Consequently,
table data was blank in the dashboard UI. Now, the client config
swap has been reverted and table fields should be populated in the
dashboard UI.

Revert client change

Update wrangler to v1.1.0

Signed-off-by: Silvio Moioli <[email protected]>

Currently, multiple filters can be appended on the query string, and
each subsequent filter is ANDed with the set. Items that pass through
the filter set must match every filter in the set.

This change adds support for OR filters. A single filter key can specify
multiple filters, separated by ','. An item that passes this filter can
match any filter in the set.

For example, this filter matches items that have either "name" or
"namespace" that match "example":

?filter=metadata.name=example,metadata.namespace=example

This filter matches items that have "name" that matches either "foo" or
"bar":

?filter=metadata.name=foo,metadata.name=bar

Specifying more than one filter key in the query still ANDs each inner
filter set together. This set of filters can match either a name of
"foo" or "bar", but must in all cases match namespace "abc":

?filter=metadata.name=foo,metadata.name=bar&filter=metadata.namespace=abc

This change adds support for excluding results using the != operator.

Example to exclude all results with name "example":

?filter=metadata.name!=example

Include all results from namespace "example" but exclude those with name
"example":

?filter=metadata.namespace=example&metadata.name!=example

Exclude results with name "foo" OR exclude results with name "bar"
(effectively includes results of both types):

?filter=metadata.name!=foo,metadata.name!=bar

Add support for OR and NOT filters

…-11-24-39

Add initial Renovate configuration

Add a new query parameter to filter resources by their namespace or
their namespace's project. This parameter is separate from the existing
`filter` parameter.

Filter by a comma-separated list of projects and/or namespaces with:

?projectsornamespaces=p1,n1,n2

The result can be negated with the ! operator:

?projectsornamespaces!=p1,n1,n2

Change cache default to false

Add projectsornamespaces query parameter

go1.19 provides go=1.19.9, the right symbol for the major version is golang(API)

Signed-off-by: Silvio Moioli <[email protected]>

Fix drone validate build

This prevents a goroutine leak when item.Object is a `runtime.Object` but not a
`metav1.Object`, as in that case `WatchNames`’s `for` loop will quit early and
subsequent calls to `returnErr` will remain parked forever.

This helps with rancher/rancher#41225
Fuller explanation in rancher#107

…ndling

Proxy store improve error handling

Add tests

LRU cache: fix concurrent map write

Add a nested store to the proxy store to strip non-Kubernetes fields
from the object being updated.

The steve formatter and proxy store adds fields to objects when it
outputs them to the client, for usability by the UI. It adds the
object's fields[1], relationships to other objects[2], a summary of the
object's state[3], and additional information in the conditions[4].
These fields are not native to Kubernetes, so when a client submits the
object back as an update, Kubernetes reports a warning that they are
unrecognized. This change ensures the extra fields are removed before
submitting the update.

[1] https://github.com/rancher/steve/blob/bf2e9655f5dde8f55b23f67e64f0186fc68789d7/pkg/stores/proxy/proxy_store.go#L189
[2] https://github.com/rancher/steve/blob/bf2e9655f5dde8f55b23f67e64f0186fc68789d7/pkg/resources/common/formatter.go#L106
[3] https://github.com/rancher/steve/blob/bf2e9655f5dde8f55b23f67e64f0186fc68789d7/pkg/resources/common/formatter.go#L100
[4] https://github.com/rancher/steve/blob/bf2e9655f5dde8f55b23f67e64f0186fc68789d7/pkg/resources/common/formatter.go#L108

Drop unrecognized fields before update

….5.11.2

The k8s.io dependencies were bumped to latest patch for the currently
used minor. Overall changes:
- k8s.io/api v0.25.12
- k8s.io/apiextensions-apiserver v0.25.12
- k8s.io/apimachinery v0.25.12
- k8s.io/apiserver v0.25.12
- k8s.io/component-base v0.25.12
- k8s.io/kube-aggregator v0.25.12
- golang.org/x/crypto v0.11.0
- golang.org/x/net v0.12.0
- golang.org/x/oauth2 v0.10.0
- golang.org/x/sync v0.3.0
- golang.org/x/sys v0.10.0
- golang.org/x/term v0.10.0
- golang.org/x/text v0.11.0
- golang.org/x/time v0.3.0

Signed-off-by: Paulo Gomes <[email protected]>

build: Bump dependencies

…m-bci-bci-base-15.x

chore(deps): update registry.suse.com/bci/bci-base docker tag to v15.5

…r-saml-0.x

chore(deps): update module github.com/rancher/saml to v0.2.0

…r-remotedialer-0.x

chore(deps): update module github.com/rancher/remotedialer to v0.3.0

…a-websocket-1.x

chore(deps): update module github.com/gorilla/websocket to v1.5.0

…-bci-bci-micro-15.x

chore(deps): update registry.suse.com/bci/bci-micro docker tag to v15.5.11.2

…-cli-1.x

chore(deps): update module github.com/urfave/cli to v1.22.14

…r-kubernetes-provider-detector-0.x

chore(deps): update module github.com/rancher/kubernetes-provider-detector to v0.1.5

…16.0