Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
K
k3s
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jacklull
  • k3s
  • Repository

Switch branch/tag
  • k3s
  • README.md
Find file
BlameHistoryPermalink
  • Hyeon Kim's avatar
    README.md: k3s does not exclude legacy/alpha/non-default features anymore · 14efc640
    Hyeon Kim authored Dec 10, 2019
    In the past, yes k3s did exclude all those legacy, alpha, non-default
    features from Kubernetes source as you can see in
    https://github.com/rancher/k3s/pull/113. But not anymore.
    
    As you can see in the source code, most of legacy/alpha/non-default
    features is available in k3s, and misleading README should be updated.
    
    But please, don't get me wrong. I'm actually glad to see those features
    enabled in k3s. :)
    
    Reference:
      https://github.com/kubernetes/kubernetes/compare/v1.16.3...rancher:v1.16.3-k3s.1
    14efc640
README.md 2.28 KB
EditWeb IDE

Replace README.md

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.