Bump github.com/hashicorp/vault/api/auth/kubernetes from 0.3.0 to 0.4.0

[dependabot]

Bumps github.com/hashicorp/vault/api/auth/kubernetes from 0.3.0 to 0.4.0.

Changelog

Sourced from github.com/hashicorp/vault/api/auth/kubernetes's changelog.

0.4.0 (December 10, 2015)

DEPRECATIONS/CHANGES:

• Policy Name Casing: Policy names are now normalized to lower-case on write, helping prevent accidental case mismatches. For backwards compatibility, policy names are not currently normalized when reading or deleting. GH-676
• Default etcd port number: the default connection string for the etcd physical store uses port 2379 instead of port 4001, which is the port used by the supported version 2.x of etcd. GH-753
• As noted below in the FEATURES section, if your Vault installation contains a policy called default, new tokens created will inherit this policy automatically.
• In the PKI backend there have been a few minor breaking changes:
  • The token display name is no longer a valid option for providing a base domain for issuance. Since this name is prepended with the name of the authentication backend that issued it, it provided a faulty use-case at best and a confusing experience at worst. We hope to figure out a better per-token value in a future release.
  • The allowed_base_domain parameter has been changed to allowed_domains, which accepts a comma-separated list of domains. This allows issuing certificates with DNS subjects across multiple domains. If you had a configured allowed_base_domain parameter, it will be migrated automatically when the role is read (either via a normal read, or via issuing a certificate).

FEATURES:

• Significantly Enhanced PKI Backend: The pki backend can now generate and sign root CA certificates and intermediate CA CSRs. It can also now sign submitted client CSRs, as well as a significant number of other enhancements. See the updated documentation for the full API. GH-666
• CRL Checking for Certificate Authentication: The cert backend now supports pushing CRLs into the mount and using the contained serial numbers for revocation checking. See the documentation for the cert backend for more info. GH-330
• Default Policy: Vault now ensures that a policy named default is added to every token. This policy cannot be deleted, but it can be modified (including to an empty policy). There are three endpoints allowed in the default default policy, related to token self-management: lookup-self, which allows a token to retrieve its own information, and revoke-self and renew-self, which are self-explanatory. If your existing Vault installation contains a policy called default, it will not be overridden, but it will be added to each new token created. You can override this behavior when using manual token creation (i.e. not via an authentication backend) by setting the "no_default_policy" flag to true. GH-732

IMPROVEMENTS:

• api: API client now uses a 60 second timeout instead of indefinite GH-681

... (truncated)

Commits

• b3da917 Cut version 0.4.0
• d597ae2 Fill in release date in Changelog
• ba44fb4 Bump website version
• b3786fb Add check for DOCKER_CROSS_IMAGE in dist script
• 583882e Update documentation to be consistent with return codes
• c1151dd Merge pull request #666 from hashicorp/pki-csrs
• a09b2f3 Make the timeout for 'make test' 60s to accommodate larger numbers of generat...
• 22cb3ae Merge branch 'master' into pki-csrs
• 53b5bbe Merge pull request #826 from hashicorp/issue-825
• 53c363d Return 400 instead of 500 if generic backend is written to without data.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #1755.