Tested with `kind` and GKE. Note: "nodes" shown in `docker buildx ls` are unrelated to Kubernetes "nodes". Probably buildx should come up with an alternative term. Usage: $ kind create cluster $ export KUBECONFIG="$(kind get kubeconfig-path --name="kind")" $ docker buildx create --driver kubernetes --driver-opt replicas=3 --use $ docker buildx build -t foo --load . `--load` loads the image into the local Docker. Driver opts: - `image=IMAGE` - Sets the container image to be used for running buildkit. - `namespace=NS` - Sets the Kubernetes namespace. Defaults to the current namespace. - `replicas=N` - Sets the number of `Pod` replicas. Defaults to 1. - `rootless=(true|false)` - Run the container as a non-root user without `securityContext.privileged`. Defaults to false. - `loadbalance=(sticky|random)` - Load-balancing strategy. If set to "sticky", the pod is chosen using the hash of the context path. Defaults to "sticky" Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
53 lines
1.6 KiB
Go
53 lines
1.6 KiB
Go
package gophercloud
|
|
|
|
/*
|
|
AuthResult is the result from the request that was used to obtain a provider
|
|
client's Keystone token. It is returned from ProviderClient.GetAuthResult().
|
|
|
|
The following types satisfy this interface:
|
|
|
|
github.com/gophercloud/gophercloud/openstack/identity/v2/tokens.CreateResult
|
|
github.com/gophercloud/gophercloud/openstack/identity/v3/tokens.CreateResult
|
|
|
|
Usage example:
|
|
|
|
import (
|
|
"github.com/gophercloud/gophercloud"
|
|
tokens2 "github.com/gophercloud/gophercloud/openstack/identity/v2/tokens"
|
|
tokens3 "github.com/gophercloud/gophercloud/openstack/identity/v3/tokens"
|
|
)
|
|
|
|
func GetAuthenticatedUserID(providerClient *gophercloud.ProviderClient) (string, error) {
|
|
r := providerClient.GetAuthResult()
|
|
if r == nil {
|
|
//ProviderClient did not use openstack.Authenticate(), e.g. because token
|
|
//was set manually with ProviderClient.SetToken()
|
|
return "", errors.New("no AuthResult available")
|
|
}
|
|
switch r := r.(type) {
|
|
case tokens2.CreateResult:
|
|
u, err := r.ExtractUser()
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
return u.ID, nil
|
|
case tokens3.CreateResult:
|
|
u, err := r.ExtractUser()
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
return u.ID, nil
|
|
default:
|
|
panic(fmt.Sprintf("got unexpected AuthResult type %t", r))
|
|
}
|
|
}
|
|
|
|
Both implementing types share a lot of methods by name, like ExtractUser() in
|
|
this example. But those methods cannot be part of the AuthResult interface
|
|
because the return types are different (in this case, type tokens2.User vs.
|
|
type tokens3.User).
|
|
*/
|
|
type AuthResult interface {
|
|
ExtractTokenID() (string, error)
|
|
}
|