Search Options

Results per page
Sort
Preferred Languages
Advance

Results 21 - 30 of 765 for issuer (0.06 sec)

  1. cmd/sts-handlers.go

    	claims[expClaim] = UTCNow().Add(expiry).Unix()
    	claims[subClaim] = certificate.Subject.CommonName
    	claims[audClaim] = certificate.Subject.Organization
    	claims[issClaim] = certificate.Issuer.CommonName
    	claims[parentClaim] = parentUser
    	secretKey, err := getTokenSigningKey()
    	if err != nil {
    		writeSTSErrorResponse(ctx, w, ErrSTSInternalError, err)
    		return
    	}
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Aug 15 01:29:20 UTC 2024
    - 33.9K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.4.md

    ## Known Issues
    
    - Completed pods lose logs across node upgrade ([#32324](https://github.com/kubernetes/kubernetes/issues/32324))
    - Pods are deleted across node upgrade ([#32323](https://github.com/kubernetes/kubernetes/issues/32323))
    - Secure master -> node communication ([#11816](https://github.com/kubernetes/kubernetes/issues/11816))
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu Dec 24 02:28:26 UTC 2020
    - 133.5K bytes
    - Viewed (0)
  3. CHANGELOG/CHANGELOG-1.13.md

    - When using IPV6-only, be sure to use `proxy-mode=iptables` as `proxy-mode=ipvs` is known to not work. ([#68437](https://github.com/kubernetes/kubernetes/issues/68437))
    
    ## Deprecations
    
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu May 05 13:44:43 UTC 2022
    - 273.1K bytes
    - Viewed (0)
  4. CHANGELOG/CHANGELOG-1.3.md

      - [Highlights](#highlights)
      - [Known Issues and Important Steps before Upgrading](#known-issues-and-important-steps-before-upgrading)
          - [ThirdPartyResource](#thirdpartyresource)
          - [kubectl](#kubectl)
          - [kubernetes Core Known Issues](#kubernetes-core-known-issues)
          - [Docker runtime Known Issues](#docker-runtime-known-issues)
          - [Rkt runtime Known Issues](#rkt-runtime-known-issues)
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu Dec 24 02:28:26 UTC 2020
    - 84K bytes
    - Viewed (0)
  5. .github/workflows/issue-metadata.yml

    name: Check issues metadata
    
    on:
      issues:
        types: [ opened, unlabeled, closed ]
    
    permissions: {}
    
    jobs:
      check_issue_metadata:
        permissions:
          issues: write
        runs-on: ubuntu-latest
        steps:
          # Check that issues have proper metadata: labels and milestone
          # https://github.com/gradle/issue-management-action/blob/main/src/issue-metadata.ts
    Registered: Wed Nov 06 11:36:14 UTC 2024
    - Last Modified: Mon Jun 17 13:58:59 UTC 2024
    - 429 bytes
    - Viewed (0)
  6. .github/workflows/issues.yaml

    # @format
    
    name: Issue Workflow
    
    on:
      issues:
        types:
          - opened
    
    jobs:
      add-to-project:
        name: Add issue to project
        runs-on: ubuntu-latest
        steps:
          - uses: actions/add-to-project@v0.5.0
            with:
              project-url: https://github.com/orgs/miniohq/projects/2
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Jan 11 07:02:00 UTC 2024
    - 338 bytes
    - Viewed (0)
  7. .github/workflows/stale-issues.yml

              days-before-issue-close: 7
              stale-issue-label: "stale"
              # reason for closed the issue default value is not_planned
              close-issue-reason: completed
              # List of labels to remove when issues/PRs unstale. 
              labels-to-remove-when-unstale: 'stat:awaiting response'
              only-labels: "stat:awaiting response"
              stale-issue-message: > 
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Wed Jun 26 15:41:19 UTC 2024
    - 4.1K bytes
    - Viewed (0)
  8. .github/workflows/issue-manager.yml

    name: Issue Manager
    
    on:
      schedule:
        - cron: "13 22 * * *"
      issue_comment:
        types:
          - created
      issues:
        types:
          - labeled
      pull_request_target:
        types:
          - labeled
      workflow_dispatch:
    
    permissions:
      issues: write
      pull-requests: write
    
    jobs:
      issue-manager:
        if: github.repository_owner == 'fastapi'
        runs-on: ubuntu-latest
        steps:
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Tue Oct 15 10:38:53 UTC 2024
    - 1.4K bytes
    - Viewed (0)
  9. .github/workflows/issue-on-pr-rollback.yml

    name: Creates a GitHub Issue when a PR Rolled back via Commit to Master
    on:
      push:
        branches:
          - master
          
    permissions: {}
    
    jobs:
      create-issue-on-pr-rollback:
        runs-on: ubuntu-latest
        permissions:
          contents: read
          issues: write
          pull-requests: read
        if: |
          github.repository == 'tensorflow/tensorflow' &&
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Fri Nov 01 08:40:10 UTC 2024
    - 1.5K bytes
    - Viewed (0)
  10. ISSUES.md

    If you open a GitHub Issue, here is our policy:
    
    1.  It must be a bug/performance issue or a feature request or a build issue or
        a documentation issue (for small doc fixes please send a PR instead).
    1.  Make sure the Issue Template is filled out.
    1.  The issue should be related to the repo it is created in.
    
    **Here's why we have this policy:** We want to focus on the work that benefits
    the whole community, e.g., fixing bugs and adding features. Individual support
    Registered: Tue Nov 05 12:39:12 UTC 2024
    - Last Modified: Thu Feb 11 22:37:27 UTC 2021
    - 606 bytes
    - Viewed (0)
Back to top