Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: unable to recognize "daemonset.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1" #2084

Closed
joeldeteves opened this issue Apr 5, 2020 · 3 comments

Comments

@joeldeteves
Copy link

Bug Report

Describe the bug
In the fluent-bit docs, it says when using version 1.4x to replace

apiVersion: apps/v1

with

apiVersion: extensions/v1beta1

However I am presented with the following error:
error: unable to recognize "fluent-bit-ds.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

It seems extensions/v1beta1 has been deprecated according to the Kubernetes changelogs for version 1.16.x:
https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.16.md#deprecations-and-removals

To Reproduce

  • Steps to reproduce the problem:
    Try to apply the fluent-bit daemonset on Kubernetes v1.16.6 or higher

Expected behavior
fluent-bit should revert to using apps/v1 as per Kubernetes documentation

Screenshots
N/A

Your Environment

  • Version used: Fluent-bit version 1.4.2
  • Configuration:
  • Environment name and version (e.g. Kubernetes? What version?): DOKS (Digital Ocean Managed Kubernetes) version 1.16.6
  • Server type and version: N/A
  • Operating System and version: Ubuntu 18.04
  • Filters and plugins: N/A

Additional context
I am unable to upgrade Fluent-bit to version 1.4x

@edsiper
Copy link
Member

edsiper commented Apr 5, 2020 via email

@pmalek
Copy link

pmalek commented Jun 28, 2020

@edsiper The link you've provided describes a situation when a kubernetes version lower than v1.16 is used whereas @joeldeteves uses v1.16.6 which deprecates apiVersion: extensions/v1beta1 which is mentioned there.

There's a PR that seems to fix this issue: fluent/fluent-bit-kubernetes-logging#79

@edsiper
Copy link
Member

edsiper commented Nov 18, 2021

closing as it's already fixed on fluent/fluent-bit-kubernetes-logging#79

@edsiper edsiper closed this as completed Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants