Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • H helm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 1105 Внедрение механизмов обеспечения безопасности цепочки поставки программных проектов
  • LegacyLegacy
  • scanned-projects
  • helm
  • Repository
  • helm
  • pkg
  • kube
  • result.go
Find file BlameHistoryPermalink
  • Maxim Ivanov's avatar
    When looking for original resource on update/delete, ignore Apiversion, use Kind and Name only · bed80e48
    Maxim Ivanov authored Sep 27, 2017
    Kind can change it's APIVersion with time, such as "Deployment" which was
    "extensions/v1beta1" and then migrated to "apps/v1beta1" in Kube 1.6.
    
    Name, Kind and optinally Namespace are used to find relevant Info
    object for a original resource which is being upgraded, it safe enough,
    as it is uniquely identifies an object.
    bed80e48