te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>Azure DevOps create new pipeline for Deploy Azure Kubernetes Services private cluster encounter error - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>Azure DevOps create new pipeline for Deploy Azure Kubernetes Services private cluster encounter error - Stack Overflow

    Azure DevOps create new pipeline for Deploy Azure Kubernetes Services private cluster encounter error - Stack Overflow

    programmeradmin3浏览0评论

    I am using Azure DevOps create pipeline for deploy to azure kubernetes service. during create new pipeline for Deploy Azure Kubernetes Services private cluster encounter error like below.

    on azure devops already create services principle for connection to AKS

    Create pipeline error

    Some user found like this.

    How should I fix it?

    BR, Za_phu

    I am using Azure DevOps create pipeline for deploy to azure kubernetes service. during create new pipeline for Deploy Azure Kubernetes Services private cluster encounter error like below.

    on azure devops already create services principle for connection to AKS

    Create pipeline error

    Some user found like this.

    How should I fix it?

    BR, Za_phu

    • azure-devops
    • azure-pipelines
    • azure-aks
    Share Improve this question asked Feb 18 at 1:03 powerfulpowerful 572 silver badges8 bronze badges
    Add a comment  | 

    1 Answer 1

    Reset to default -2

    When you use "Deploy to Azure Kubernetes Service" template to create an Azure pipeline, Azure DevOps will access your Subscription and resources inside it. If the user doesn't have permissions to access the Subscription/AKS, he will get permission-related error as shown in your second screenshot.

    About error "The remote name could not be resolved "..azmk8s.io", it's a DNS resolution issue with your Azure Kubernetes Service (AKS) cluster. Please

    • Ensure that your AKS cluster's DNS configuration is correct.
    • Ensure that your network settings allow connectivity from Azure DevOps to the AKS cluster. Ensure that there are no firewall rules or network security groups blocking access.

    As a workaround, you can create a pipeline manually and use the service connection created before. The following YAML is automatically created. Replace parameters with your actual values. If your AKS has Vnet configured, you may consider add the ip of MS-hosted agent to your allow list or set up a self-hosted agent in the same network.

    # Deploy to Azure Kubernetes Service
# Build and push image to Azure Container Registry; Deploy to Azure Kubernetes Service
# https://docs.microsoft/azure/devops/pipelines/languages/docker

trigger:
- main

resources:
- repo: self

variables:

  # Container registry service connection established during pipeline creation
  dockerRegistryServiceConnection: '{DockerRegistrySC}'
  imageRepository: '{ImageName}'
  containerRegistry: '{RegistryName}.azurecr.io'
  dockerfilePath: '**/Dockerfile'
  tag: '$(Build.BuildId)'
  imagePullSecret: '{SecretName}'

  # Agent VM image name
  vmImageName: 'ubuntu-latest'


stages:
- stage: Build
  displayName: Build stage
  jobs:
  - job: Build
    displayName: Build
    pool:
      vmImage: $(vmImageName)
    steps:
    - task: Docker@2
      displayName: Build and push an image to container registry
      inputs:
        command: buildAndPush
        repository: $(imageRepository)
        dockerfile: $(dockerfilePath)
        containerRegistry: $(dockerRegistryServiceConnection)
        tags: |
          $(tag)

    - upload: manifests
      artifact: manifests

- stage: Deploy
  displayName: Deploy stage
  dependsOn: Build

  jobs:
  - deployment: Deploy
    displayName: Deploy
    pool:
      vmImage: $(vmImageName)
    environment: 'pipelinesjavascriptdocker.default'
    strategy:
      runOnce:
        deploy:
          steps:
          - task: KubernetesManifest@0
            displayName: Create imagePullSecret
            inputs:
              action: createSecret
              secretName: $(imagePullSecret)
              dockerRegistryEndpoint: $(dockerRegistryServiceConnection)

          - task: KubernetesManifest@0
            displayName: Deploy to Kubernetes cluster
            inputs:
              action: deploy
              manifests: |
                $(Pipeline.Workspace)/manifests/deployment.yml
                $(Pipeline.Workspace)/manifests/service.yml
              imagePullSecrets: |
                $(imagePullSecret)
              containers: |
                $(containerRegistry)/$(imageRepository):$(tag)
    继续浏览有关 的文章

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论